[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Thanks for the quick fix! Will this fix also apply for 18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
ah, good point. I was on 5.4.X so this fix should work for 18.04 running that kernel as well. thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579748] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption
Lenovo g580 The bug is present on the last hwe kernel 4.10.0-30-generic I'll try to test the solution https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579748/comments/24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1579748 Title: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption Status in linux package in Ubuntu: Incomplete Bug description: RTS5129 Card Reader has issues with rtsx_usb module on kernels >=3.16 (since kmod-staging rts5129 module replaced with rtsx). Copying files from FAT32 SDHC memory card produces error messages in syslog: May 9 05:39:15 dev-laptop kernel: [ 134.762713] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900 May 9 05:39:15 dev-laptop kernel: [ 135.427035] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900 May 9 05:39:16 dev-laptop kernel: [ 136.030041] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900 Also these errors indicate that copied files are corrupted - md5sum shows different checksums for copied file after each "insert card/copy file/check md5sum/eject card" cycle (actually you can skip "copy file" step and run "check md5sum" step directly with file on mounted memory card filesystem). Running sudo badblocks -n /dev/mmcblk0 produces same error messages and prints a lot of random block numbers. Hardware: - dell inspiron 7720 laptop (a few different RAM modules and HDD drives used for testing); - Realtek Semiconductor Corp. RTS5129 Card Reader (ID 0bda:0129); - Transcend 32Gb SDHC Memory card Class 10 UHS-I. Bug exists in latest xenial 4.4.0-22.39 kernel and xenial mainline 4.4.9-040409_4.4.9-040409.201605041832. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dev1692 F pulseaudio CurrentDesktop: Unity Date: Mon May 9 08:38:14 2016 HibernationDevice: RESUME=UUID=cf073128-d53a-4214-96bc-3acdf0516900 InstallationDate: Installed on 2016-05-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Inspiron 7720 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=2e4e4944-669a-4f1b-a080-87971c644984 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 04M3YM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd08/23/2013:svnDellInc.:pnInspiron7720:pvr:rvnDellInc.:rn04M3YM:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7720 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1579748] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption
compile https://github.com/asymingt/rts5139 Linux oleg-Lenovo-G580 4.10.0-30-generic #34~16.04.1-Ubuntu SMP Wed Aug 2 02:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [10366.363560] sd 6:0:0:0: [sdb] 7954432 512-byte logical blocks: (4.07 GB/3.79 GiB) [10376.625609] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [10376.625618] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] [10376.625623] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error [10376.625630] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [10376.625634] blk_update_request: critical medium error, dev sdb, sector 0 [10376.625646] Buffer I/O error on dev sdb, logical block 0, async page read [10386.866325] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [10386.866333] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] [10386.866338] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error [10386.866345] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [10386.866350] blk_update_request: critical medium error, dev sdb, sector 0 [10386.866360] Buffer I/O error on dev sdb, logical block 0, async page read [10397.107027] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [10397.107031] sd 6:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] [10397.107033] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read error [10397.107036] sd 6:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [10397.107038] blk_update_request: critical medium error, dev sdb, sector 0 [10397.107043] Buffer I/O error on dev sdb, logical block 0, async page read [10397.107056] ldm_validate_partition_table(): Disk read failed. # lsmod Module Size Used by hid_generic16384 0 usbhid 53248 0 hid 118784 2 hid_generic,usbhid rfcomm 77824 12 pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 458752 3 vboxnetadp,vboxnetflt,vboxpci zram 24576 4 bnep 20480 2 rts5139 315392 0 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc videobuf2_v4l2 24576 1 uvcvideo videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2 videodev 172032 3 uvcvideo,videobuf2_core,videobuf2_v4l2 media 40960 2 uvcvideo,videodev btusb 45056 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb bluetooth 557056 39 btrtl,btintel,bnep,btbcm,rfcomm,btusb wl 6447104 0 intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 kvm_intel 200704 0 kvm 593920 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 cryptd 24576 1 ghash_clmulni_intel intel_cstate 20480 0 intel_rapl_perf16384 0 joydev 20480 0 input_leds 16384 0 serio_raw 16384 0 snd_hda_codec_hdmi 49152 1 snd_hda_codec_conexant24576 1 snd_hda_codec_generic73728 1 snd_hda_codec_conexant snd_hda_intel 36864 3 snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic snd_hda_core 81920 5 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic snd_hwdep 16384 1 snd_hda_codec snd_pcm 102400 4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi snd_seq_midi 16384 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi32768 1 snd_seq_midi snd_seq65536 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 32768 2 snd_seq,snd_pcm ideapad_laptop 24576 0 lpc_ich24576 0 mei_me 40960 0 snd77824 17 snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_pcm cfg80211 602112 1 wl sparse_keymap 16384 1 ideapad_laptop wmi16384 1 ideapad_laptop mei 102400 1 mei_me shpchp 36864 0 soundcore 16384 1 snd mac_hid16384 0 coretemp 16384 0 bbswitch 16384 0 parport_pc 32768 0 ppdev 20480 0 lp 20480 0 parport49152 3 lp,parport_pc,ppdev autofs440960 2 btrfs
[Kernel-packages] [Bug 1579748] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption
returm to kernel driver and change in drivers/mmc/host/rtsx_usb_sdmmc.c
As advised in https://lkml.org/lkml/2015/10/21/318 comment caps:
static void rtsx_usb_init_host(struct rtsx_usb_sdmmc *host)
{
struct mmc_host *mmc = host->mmc;
mmc->f_min = 25;
mmc->f_max = 20800;
mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34 | MMC_VDD_165_195;
mmc->caps = MMC_CAP_4_BIT_DATA | MMC_CAP_SD_HIGHSPEED |
// MMC_CAP_MMC_HIGHSPEED | MMC_CAP_BUS_WIDTH_TEST |
// MMC_CAP_UHS_SDR12 | MMC_CAP_UHS_SDR25 | MMC_CAP_UHS_SDR50 |
MMC_CAP_NEEDS_POLL;
mmc->caps2 = MMC_CAP2_NO_PRESCAN_POWERUP | MMC_CAP2_FULL_PWR_CYCLE;
mmc->max_current_330 = 400;
mmc->max_current_180 = 800;
mmc->ops = &rtsx_usb_sdmmc_ops;
mmc->max_segs = 256;
mmc->max_seg_size = 65536;
mmc->max_blk_size = 512;
mmc->max_blk_count = 65535;
mmc->max_req_size = 524288;
host->power_mode = MMC_POWER_OFF;
}
reload new module and block rts5139
# lsmod | grep rts
rtsx_usb_sdmmc 28672 0
rtsx_usb_ms20480 0
memstick 16384 1 rtsx_usb_ms
rtsx_usb 20480 2 rtsx_usb_sdmmc,rtsx_usb_ms
It does not work anyway, as before the changes:
[10270.437734] mmc0: error -110 whilst initialising SD card
[10273.125682] mmc0: error -110 whilst initialising SD card
[10276.837684] mmc0: error -110 whilst initialising SD card
[10279.493425] mmc0: error -110 whilst initialising SD card
[10304.740718] mmc0: error -110 whilst initialising SD card
[10307.428683] mmc0: error -110 whilst initialising SD card
If you have any ideas I can check them on my kernel
Linux oleg-Lenovo-G580 4.10.0-30-generic #34~16.04.1-Ubuntu SMP Wed Aug
2 02:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1579748
Title:
rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader
Controller: mmc errors and read data corruption
Status in linux package in Ubuntu:
Incomplete
Bug description:
RTS5129 Card Reader has issues with rtsx_usb module on kernels >=3.16
(since kmod-staging rts5129 module replaced with rtsx).
Copying files from FAT32 SDHC memory card produces error messages in syslog:
May 9 05:39:15 dev-laptop kernel: [ 134.762713] mmcblk0: error -110 sending
stop command, original cmd response 0x900, card status 0x900
May 9 05:39:15 dev-laptop kernel: [ 135.427035] mmcblk0: error -110 sending
stop command, original cmd response 0x900, card status 0x900
May 9 05:39:16 dev-laptop kernel: [ 136.030041] mmcblk0: error -110 sending
stop command, original cmd response 0x900, card status 0x900
Also these errors indicate that copied files are corrupted - md5sum
shows different checksums for copied file after each "insert card/copy
file/check md5sum/eject card" cycle (actually you can skip "copy file"
step and run "check md5sum" step directly with file on mounted memory
card filesystem).
Running sudo badblocks -n /dev/mmcblk0 produces same error messages
and prints a lot of random block numbers.
Hardware:
- dell inspiron 7720 laptop (a few different RAM modules and HDD drives used
for testing);
- Realtek Semiconductor Corp. RTS5129 Card Reader (ID 0bda:0129);
- Transcend 32Gb SDHC Memory card Class 10 UHS-I.
Bug exists in latest xenial 4.4.0-22.39 kernel and xenial mainline
4.4.9-040409_4.4.9-040409.201605041832.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.39
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dev1692 F pulseaudio
CurrentDesktop: Unity
Date: Mon May 9 08:38:14 2016
HibernationDevice: RESUME=UUID=cf073128-d53a-4214-96bc-3acdf0516900
InstallationDate: Installed on 2016-05-08 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 7720
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic
root=UUID=2e4e4944-669a-4f1b-a080-87971c644984 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-22-generic N/A
linux-backports-modules-4.4.0-22-generic N/A
linux-firmware1.157
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 04M3YM
dmi.board.ven
[Kernel-packages] [Bug 1579748] Re: rtsx_usb module for Realtek Semiconductor Corp. RTS5129 Card Reader Controller: mmc errors and read data corruption
install this kernel: oleg@oleg-Lenovo-G580:~/Завантаження/1$ sudo dpkg -i *.deb [sudo] пароль до oleg: (Читання бази даних ... на дану мить встановлено 315002 файли та каталоги.) Приготування до розпакування linux-headers-4.13.0-5_4.13.0-5.6_all.deb ... Розпакування linux-headers-4.13.0-5 (4.13.0-5.6) над (4.13.0-5.6)... Приготування до розпакування linux-headers-4.13.0-5-generic_4.13.0-5.6_amd64.deb ... Розпакування linux-headers-4.13.0-5-generic (4.13.0-5.6) над (4.13.0-5.6)... Приготування до розпакування linux-image-4.13.0-5-generic_4.13.0-5.6_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic Done. Розпакування linux-image-4.13.0-5-generic (4.13.0-5.6) над (4.13.0-5.6)... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic Приготування до розпакування linux-image-extra-4.13.0-5-generic_4.13.0-5.6_amd64.deb ... Розпакування linux-image-extra-4.13.0-5-generic (4.13.0-5.6) над (4.13.0-5.6)... Налаштовування linux-headers-4.13.0-5 (4.13.0-5.6) ... Налаштовування linux-headers-4.13.0-5-generic (4.13.0-5.6) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic ERROR (dkms apport): kernel package linux-headers-4.13.0-5-generic is not supported Error! Bad return status for module build on kernel: 4.13.0-5-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.13.0-5-generic is not supported Error! Bad return status for module build on kernel: 4.13.0-5-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information. Налаштовування linux-image-4.13.0-5-generic (4.13.0-5.6) ... Running depmod. update-initramfs: deferring update (hook will be called later) Not updating initrd symbolic links since we are being updated/reinstalled (4.13.0-5.6 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (4.13.0-5.6 was configured last, according to dpkg) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic ERROR (dkms apport): kernel package linux-headers-4.13.0-5-generic is not supported Error! Bad return status for module build on kernel: 4.13.0-5-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ERROR (dkms apport): kernel package linux-headers-4.13.0-5-generic is not supported Error! Bad return status for module build on kernel: 4.13.0-5-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-5-generic /boot/vmlinuz-4.13.0-5-generic update-initramfs: Generating /boot/initrd.img-4.13.0-5-generic
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
I tried different kernels, settings, even instructions from #140 post of this thread... Nothing could help. But some distros worked fine on this laptop - for example Manjaro and CentOS (waking up from suspend without issues). On my Lenovo s205 the only installing "tlp" and "tlp-rdw" (Linux Advanced Power Management) solved problem with freezing after suspend. The Kernel I'm using is 4.4.0-62-generic (Linux Mint 18.1). More about "tpl" here: http://linrunner.de/en/tlp/docs/tlp-linux- advanced-power-management.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531105] Re: [Lenovo Ideapad S205] suspend/resume failure
Linux Mint 18.1 64bit (Kernel 4.4.0-62-generic). Lenovo s205 successfully wakes up after suspend (without battery, only AC/DC plugged in)! Only after installing "tlp". Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531105 Title: [Lenovo Ideapad S205] suspend/resume failure Status in linux package in Ubuntu: Triaged Bug description: tux@S205:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 tux@S205:~$ apt-cache policy linux-image-generic linux-image-generic: Asennettu: 4.3.0.5.6 Ehdokas: 4.3.0.5.6 Versiotaulukko: *** 4.3.0.5.6 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status ProblemType: KernelOops DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-5-generic 4.3.0-5.16 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic i686 Annotation: This occurred during a previous suspend, and prevented the system from resuming properly. ApportVersion: 2.19.3-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tux1354 F pulseaudio /dev/snd/controlC0: tux1354 F pulseaudio Date: Tue Jan 5 10:05:18 2016 DuplicateSignature: suspend/resume:LENOVO Brazos:4BCN21WW ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1449740259 Failure: suspend/resume HibernationDevice: RESUME=UUID=32b9aa72-b625-487e-a5b8-6b621d567c76 InstallationDate: Installed on 2016-01-05 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160104) InterpreterPath: /usr/bin/python3.5 MachineType: LENOVO Brazos ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=ffc5ca30-e3d6-4ca6-a574-c11aa8214ab9 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.154 SourcePackage: linux Title: [LENOVO Brazos] suspend/resume failure UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/23/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4BCN21WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: 109-B78210-00A dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr4BCN21WW:bd05/23/2011:svnLENOVO:pnBrazos:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.name: Brazos dmi.product.version: Ideapad S205 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
*** This bug is a duplicate of bug 1531747 *** https://bugs.launchpad.net/bugs/1531747 ** This bug has been marked a duplicate of bug 1531747 overlay: mkdir fails if directory exists in lowerdir in a user namespace -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490267] Re: Regression in overlayfs
I can no longer reproduce this bug, following the release of fixes for bugs #1531747, #1534961 and #1535150 . ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490267 Title: Regression in overlayfs Status in linux package in Ubuntu: Fix Released Bug description: When installing the linux-lts-vivid kernel in Ubuntu 14.04, there is a regression with overlayfs and unprivileged containers: 'failed to whiteout' Below the system information: - Kernel error: http://pastebin.com/iajXHbHZ - Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - Executed LXC command: lxc-clone -s -B overlayfs orig test (both unprivileged containers) - LXC version: 1.0.7 We discussed this on the LXC user mailing list, and this is likely a bug in one of the patches that add support for unprivileged use of overlayfs. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 13:56 seq crw-rw 1 root audio 116, 33 Aug 30 13:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-fceee9e1 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-central-1b Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb 1 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=dde0e30e-be54-43dc-9a44-5769353c2e27 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory StagingDrivers: visorutil Tags: trusty ec2-images staging Uname: Linux 3.19.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade
Same issue after upgraded from 15.04 on Samsung ATIV Book 8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: suspend not working after uprade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
This bug affects the 4.4 kernel, including the xenial kernel and the lts-xenial kernel in trusty. The linked freedesktop bug report mentions that the bug was fixed in the 4.5 kernel with the following commit, http://kernel.ubuntu.com/git/ubuntu/linux.git/commit/?id=92826fcdfc147a7d16766e987c12a9dfe1860c3f The commit was not backported to the 4.4 kernel, and is not present in the xenial kernel. I initially tested the 4.5 mainline kernel and found that it does fix the bug. I then attempted to apply the aforementioned commit to the xenial kernel and found that it does not apply cleanly. By including two earlier patches I was able to get it to apply (with minor porting). But the resultant kernel did not fix the bug. Details: The two earlier patches are: drm/i915/ivb: Move WaCxSRDisabledForSpriteScaling w/a to atomic check, d21fbe87ce18297af0a9b7cc0cd545fd9ac28d33 drm/i915: Move disable_cxsr to the crtc_state, ab1d3a0e5a44f5b1a8d1f811e925c8519b56fba4 ** Patch removed: "drm/i915: Calculate watermark related members in the crtc_state, v4." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/+attachment/4639342/+files/patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
** Tags removed: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
A reverse-bisect (as per comment #8) shows that the first good commit is: commit 14de6c44d149c68df1800ded42bbab51485ef67a Author: Maarten Lankhorst drm/atomic: Remove drm_atomic_connectors_for_crtc. ** Tags removed: needs-reverse-bisect ** Tags added: bisect-done ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
Applying the following two cherry-picks to the xenial (Ubuntu-4.4.0-22.39) kernel solves the bug for my hardware, git cherry-pick 4cd3991 git am 0001-drm-atomic-Remove-drm_atomic_connectors_for_crtc.patch # 14de6c4 does not apply cleanly, so use the attached patch [For the mainline (v4.4.9) kernel, I have not figured out a minimal set of cherry-picks.] ** Patch added: "0001-drm-atomic-Remove-drm_atomic_connectors_for_crtc.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/+attachment/4659364/+files/0001-drm-atomic-Remove-drm_atomic_connectors_for_crtc.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
In comment #33, commit 4cd3991 is superfluous. I have verified that the bug can be fixed on my hardware by applying a single cherry-pick to the xenial (Ubuntu-4.4.0-22.39) kernel, git am 0001-drm-atomic-Remove-drm_atomic_connectors_for_crtc.patch # 14de6c4 backported to xenial Thanks to the following comment for suggesting that commit 4cd3991 is superfluous, https://lists.ubuntu.com/archives/kernel-team/2016-May/077206.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-lts-xenial source package in Xenial: In Progress Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580697] Re: Kernel freezes after drm_wait_one_vblank timed out
This looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1580697 Title: Kernel freezes after drm_wait_one_vblank timed out Status in linux package in Ubuntu: Confirmed Bug description: Using kernel 4.4.0 from Ubuntu GNOME 16.04 I get a lot of warnings 'drm_wait_one_vblank timed out' while booting and every time when I switch user or session via Alt-Fn. Example logs will be attached, I used this for saving the log: journalctl -b --system --no-pager |tee bootlog-$(uname -r)-$(lsb_release -sr) I suspect this may be related to some of my problems (slow switch, freeze, wrong VT: Alt-Fn6 roots to tty3) when switching virtual terminal. I see these messages on 16.04 or 14.04 when using kernel 4.4.0-21-generic, 4.4.0-22-generic or mainline kernel 4.4.0-040400-generic or 4.5.2-040502-generic, but mainline kernel 4.3.6-040306-generic does not throw this message and there are no problems with 4.3.6 while switching VT. --- ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: k2 1475 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=8e0701ee-0c76-4396-bdd9-f406da205c7b InstallationDate: Installed on 2016-03-31 (41 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta i386 (20160323.1) MachineType: FUJITSU SIEMENS LIFEBOOK E8310 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=5811fae8-2bd0-46c0-a1b3-4bd8b9f2c821 ro ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-22-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/27/2007 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNB1CE dmi.board.vendor: FUJITSU dmi.board.version: 1PCP331350-03 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E8310 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd12/27/2007:svnFUJITSUSIEMENS:pnLIFEBOOKE8310:pvr:rvnFUJITSU:rnFJNB1CE:rvr1PCP331350-03:cvnFUJITSUSIEMENS:ct10:cvrE8310: dmi.product.name: LIFEBOOK E8310 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace
FWIW, bug #1480411, "rm -r * fails to delete directories when using
overlayfs in a user-namespace", might be a duplicate of this bug. In
both bugs the script works on the host but fails in a user-namespace
with error EPERM. In this bug the operation which triggers the error is
'mkdir', while in bug #1480411 it is 'rmdir'.
The equivalent script for bug #1480411 is,
#
#!/bin/sh -ex
dir=`mktemp -d`
cleanup() {
umount -l $dir/t
rm -rf $dir
}
trap cleanup EXIT
echo "dir is $dir"
mkdir -p $dir/l $dir/u $dir/w $dir/t
mkdir $dir/l/dev
touch $dir/l/dev/foo.txt
mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
stat $dir/t/dev
rm $dir/t/dev/foo.txt
rmdir $dir/t/dev
echo $?
echo "rmdir should have succeeded"
#===
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1531747
Title:
overlay: mkdir fails if directory exists in lowerdir in a user
namespace
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Wily:
Triaged
Status in linux source package in Xenial:
Triaged
Bug description:
If a directory exists in the lowerdir but not in the mounted
overlay, then mkdir of the directory in the target dir results
in a mysterious -EPERM. I've seen this both in wily kernel
(4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
master-next (with unrelated patches added).
=
#!/bin/sh -ex
dir=`mktemp -d`
cleanup() {
umount -l $dir/t
rm -rf $dir
}
trap cleanup EXIT
echo "dir is $dir"
mkdir -p $dir/l $dir/u $dir/w $dir/t
mkdir $dir/l/dev
mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
stat $dir/t/dev
rmdir $dir/t/dev
mkdir $dir/t/dev
echo $?
echo "mkdir should have succeeded"
=
The above will work on the host, but fail in a user namespace, i.e
in a regular lxd container.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531747/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
http://kernel.ubuntu.com/git/ubuntu/linux.git/commit/?id=92826fcdfc147a7d16766e987c12a9dfe1860c3f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
author Maarten Lankhorst2015-12-03
12:49:13 (GMT)
committer Maarten Lankhorst
2015-12-07 09:56:08 (GMT)
commit 92826fcdfc147a7d16766e987c12a9dfe1860c3f (patch)
tree5d5f93ea48390b6f51328461f31d46c196b4b0c9
parent ab1d3a0e5a44f5b1a8d1f811e925c8519b56fba4 (diff)
drm/i915: Calculate watermark related members in the crtc_state, v4.
This removes pre/post_wm_update from intel_crtc->atomic, and
creates atomic state for it in intel_crtc.
Changes since v1:
- Rebase on top of wm changes.
Changes since v2:
- Split disable_cxsr into a separate patch.
Changes since v3:
- Move some of the changes to intel_wm_need_update.
Signed-off-by: Maarten Lankhorst
Link:
http://patchwork.freedesktop.org/patch/msgid/56603a49.5000...@linux.intel.com
Reviewed-by: Daniel Vetter
Diffstat
-rw-r--r-- drivers/gpu/drm/i915/intel_atomic.c 1
-rw-r--r-- drivers/gpu/drm/i915/intel_display.c39
-rw-r--r-- drivers/gpu/drm/i915/intel_drv.h2
3 files changed, 21 insertions, 21 deletions
diff --git a/drivers/gpu/drm/i915/intel_atomic.c
b/drivers/gpu/drm/i915/intel_atomic.c
index 96e3fa9..d0b1c9a 100644
--- a/drivers/gpu/drm/i915/intel_atomic.c
+++ b/drivers/gpu/drm/i915/intel_atomic.c
@@ -96,6 +96,7 @@ intel_crtc_duplicate_state(struct drm_crtc *crtc)
crtc_state->update_pipe = false;
crtc_state->disable_lp_wm = false;
crtc_state->disable_cxsr = false;
+ crtc_state->wm_changed = false;
return &crtc_state->base;
}
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index 8dcab23..a8fb7cf 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -4793,6 +4793,8 @@ intel_pre_disable_primary(struct drm_crtc *crtc)
static void intel_post_plane_update(struct intel_crtc *crtc)
{
struct intel_crtc_atomic_commit *atomic = &crtc->atomic;
+ struct intel_crtc_state *pipe_config =
+ to_intel_crtc_state(crtc->base.state);
struct drm_device *dev = crtc->base.dev;
if (atomic->wait_vblank)
@@ -4802,7 +4804,7 @@ static void intel_post_plane_update(struct intel_crtc
*crtc)
crtc->wm.cxsr_allowed = true;
- if (crtc->atomic.update_wm_post)
+ if (pipe_config->wm_changed)
intel_update_watermarks(&crtc->base);
if (atomic->update_fbc)
@@ -4835,6 +4837,9 @@ static void intel_pre_plane_update(struct intel_crtc
*crtc)
crtc->wm.cxsr_allowed = false;
intel_set_memory_cxsr(dev_priv, false);
}
+
+ if (!needs_modeset(&pipe_config->base) && pipe_config->wm_changed)
+ intel_update_watermarks(&crtc->base);
}
static void intel_crtc_disable_planes(struct drm_crtc *crtc, unsigned
plane_mask)
@@ -11696,9 +11701,14 @@ static bool intel_wm_need_update(struct drm_plane
*plane,
struct intel_plane_state *cur = to_intel_plane_state(plane->state);
/* Update watermarks on tiling or size changes. */
- if (!plane->state->fb || !state->fb ||
- plane->state->fb->modifier[0] != state->fb->modifier[0] ||
- plane->state->rotation != state->rotation ||
+ if (new->visible != cur->visible)
+ return true;
+
+ if (!cur->base.fb || !new->base.fb)
+ return false;
+
+ if (cur->base.fb->modifier[0] != new->base.fb->modifier[0] ||
+ cur->base.rotation != new->base.rotation ||
drm_rect_width(&new->src) != drm_rect_width(&cur->src) ||
drm_rect_height(&new->src) != drm_rect_height(&cur->src) ||
drm_rect_width(&new->dst) != drm_rect_width(&cur->dst) ||
@@ -11768,17 +11778,9 @@ int intel_plane_atomic_calc_changes(struct
drm_crtc_state *crtc_state,
plane->base.id, was_visible, visible,
turn_off, turn_on, mode_changed);
- if (turn_on) {
- intel_crtc->atomic.update_wm_pre = true;
- /* must disable cxsr around plane enable/disable */
- if (plane->type != DRM_PLANE_TYPE_CURSOR) {
- pipe_config->disable_cxsr = true;
- /* to potentially re-enable cxsr */
- intel_crtc->atomic.wait_vblank = true;
- intel_crtc->atomic.update_wm_post = true;
- }
- } else if (turn_off) {
- intel_crtc->atomic.update_wm_post = true;
+ if (turn_on || turn_off) {
+ pipe_config->wm_changed = true;
+
/* must disable cxsr around plane enable/disable */
if (plane->type != DRM_PLANE_TYPE_CURSOR) {
if (is_crtc_enabled)
@@ -11786,7 +11788,7 @@ int intel_plane_atomic_calc_changes(struct
drm_crtc_state *crtc_state,
pipe_config->disable_cxsr = true;
}
} else if (intel_wm_need_update(pl
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
This bug affects the 4.4 kernel, including the xenial kernel and the lts-xenial kernel in trusty. As described in the freedesktop bug report, the bug was fixed in the 4.5 kernel with the following commit, http://kernel.ubuntu.com/git/ubuntu/linux.git/commit/?id=92826fcdfc147a7d16766e987c12a9dfe1860c3f The commit was not backported to the 4.4 kernel, and is not present in the xenial kernel. The commit does apply cleanly to the 4.4 kernel and fixes the bug. Please consider applying this commit to the xenial kernel and the lts- xenial kernel in trusty. I'll attach the commit as a patch for the benefit of the bots. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-xenial (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
For some reason the link in #27 isn't registered as a patch, so I'll re- submit the patch in the hope that the bots notice it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
** Attachment added: "drm/i915: Calculate watermark related members in the crtc_state, v4." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1542939/+attachment/4639342/+files/patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1566471] Re: kernel oops: NULL pointer dereference in nfs_inode_attach_open_context+0x37/0x70 [nfs]
** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-lts-xenial (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566471 Title: kernel oops: NULL pointer dereference in nfs_inode_attach_open_context+0x37/0x70 [nfs] Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Bug description: I'm attempting to boot a Xenial server install (created from debootstrap) via NFS with overlayroot so that the initial rootfs is read-only (via NFS) and all modifications are written to a tmpfs so that I can boot many such machines. The kernel oops occurs during run- init after the initramfs has successfully mounted the NFS rootfs, created the tmpfs, and the overlayfs using both. If I do not use overlayfs, and just boot into the NFS root (read-write), then everything works. Note that the following oops was gathered from a qemu virtual machine that I netbooted, though the apport output was from real hardware. The issue occurs in both cases. Please let me know if I can provide more information. + exec run-init /root /sbin/init [9.003288] BUG: unable to handle kernel NULL pointer dereference at 0008 [9.005772] IP: [] nfs_inode_attach_open_context+0x37/0x70 [nfs] [9.007227] PGD 0 [9.007227] Oops: 0002 [#1] SMP [9.007227] Modules linked in: overlay nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy pata_acpi [9.007227] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-16-generic #32-Ubuntu [9.007227] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014 [9.007227] task: 88013ab8 ti: 88013ab88000 task.ti: 88013ab88000 [9.007227] RIP: 0010:[] [] nfs_inode_attach_open_context+0x37/0x70 [nfs] [9.007227] RSP: 0018:88013ab8bc30 EFLAGS: 00010246 [9.007227] RAX: 88007fa86d30 RBX: 8800bba16000 RCX: 0002 [9.007227] RDX: RSI: 88007fa86cc0 RDI: 8800bba16088 [9.007227] RBP: 88013ab8bc48 R08: 88007f09e09c R09: 88013b001800 [9.007227] R10: 88007fa86cc0 R11: R12: 88007fa86cc0 [9.007227] R13: 8800bba16088 R14: 8800bb9f7d88 R15: 88013a52f010 [9.007227] FS: () GS:88013fc0() knlGS: [9.007227] CS: 0010 DS: ES: CR0: 80050033 [9.007227] CR2: 0008 CR3: 00013a53 CR4: 001406f0 [9.007227] Stack: [9.007227] 88007fa86cc0 88013a52f000 8800bb9f7d88 88013ab8bc58 [9.007227] c01d153b 88013ab8bc80 c01d3d37 88013a52f000 [9.007227] 8800bb9f7d88 88013ab8bca0 c01d010d [9.007227] Call Trace: [9.007227] [] nfs_file_set_open_context+0x2b/0x30 [nfs] [9.007227] [] nfs_open+0x37/0x60 [nfs] [9.007227] [] nfs_file_open+0x4d/0x70 [nfs] [9.007227] [] do_dentry_open+0x1ff/0x310 [9.007227] [] ? nfs_file_fsync+0x130/0x130 [nfs] [9.007227] [] vfs_open+0x56/0x60 [9.007227] [] path_openat+0x1b7/0x1360 [9.007227] [] do_filp_open+0x91/0x100 [9.007227] [] ? __alloc_fd+0xc8/0x190 [9.007227] [] do_sys_open+0x13e/0x2a0 [9.007227] [] ? __put_cred+0x3d/0x50 [9.007227] [] ? SyS_access+0x1e8/0x230 [9.007227] [] SyS_open+0x1e/0x20 [9.007227] [] entry_SYSCALL_64_fastpath+0x16/0x71 [9.007227] Code: 54 53 48 8b 47 40 49 89 fc 48 8b 58 30 4c 8d ab 88 00 00 00 4c 89 ef e8 98 37 65 c1 48 8b 93 60 ff ff ff 49 8d 44 24 70 4c 89 ef <48> 89 42 08 49 89 54 24 70 48 8d 93 60 ff ff ff 49 89 54 24 78 [9.007227] RIP [] nfs_inode_attach_open_context+0x37/0x70 [nfs] [9.007227] RSP [9.007227] CR2: 0008 [9.056135] ---[ end trace 4bf38e0df912649a ]--- [9.057055] BUG: unable to handle kernel NULL pointer dereference at 0158 [9.058345] IP: [] __put_nfs_open_context+0xa0/0x100 [nfs] [9.059479] PGD 0 [9.059823] Oops: [#2] SMP [9.060117] Modules linked in: overlay nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy pata_acpi [9.060117] CPU: 0 PID: 1 Comm: init Tainted: G D 4.4.0-16-generic #32-Ubuntu [9.060117] Hardware
[Kernel-packages] [Bug 1566471] Re: kernel oops: NULL pointer dereference in nfs_inode_attach_open_context+0x37/0x70 [nfs]
On 2016-04-20 a commit was made to the upstream 4.4 stable tree which
may fix this bug (not yet tested).
nfs: use file_dentry()
NFS may be used as lower layer of overlayfs and accessing f_path.dentry
can lead to a crash. Fix by replacing direct access of
file->f_path.dentry with the file_dentry() accessor, which will always
return a native object. Fixes: 4bacc9c9234c ("overlayfs: Make f_path
always point to the overlay and f_inode to the underlay")
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.4.y&id=fda9797a6aaad1a8044614fbbdb265dda4328c41
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566471
Title:
kernel oops: NULL pointer dereference in
nfs_inode_attach_open_context+0x37/0x70 [nfs]
Status in linux package in Ubuntu:
Confirmed
Status in linux-lts-xenial package in Ubuntu:
Confirmed
Bug description:
I'm attempting to boot a Xenial server install (created from
debootstrap) via NFS with overlayroot so that the initial rootfs is
read-only (via NFS) and all modifications are written to a tmpfs so
that I can boot many such machines. The kernel oops occurs during run-
init after the initramfs has successfully mounted the NFS rootfs,
created the tmpfs, and the overlayfs using both. If I do not use
overlayfs, and just boot into the NFS root (read-write), then
everything works. Note that the following oops was gathered from a
qemu virtual machine that I netbooted, though the apport output was
from real hardware. The issue occurs in both cases. Please let me know
if I can provide more information.
+ exec run-init /root /sbin/init
[9.003288] BUG: unable to handle kernel NULL pointer dereference at
0008
[9.005772] IP: []
nfs_inode_attach_open_context+0x37/0x70 [nfs]
[9.007227] PGD 0
[9.007227] Oops: 0002 [#1] SMP
[9.007227] Modules linked in: overlay nfsv3 nfs_acl nfs lockd grace
sunrpc fscache raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear aesni_intel
aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse floppy pata_acpi
[9.007227] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-16-generic
#32-Ubuntu
[9.007227] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
[9.007227] task: 88013ab8 ti: 88013ab88000 task.ti:
88013ab88000
[9.007227] RIP: 0010:[] []
nfs_inode_attach_open_context+0x37/0x70 [nfs]
[9.007227] RSP: 0018:88013ab8bc30 EFLAGS: 00010246
[9.007227] RAX: 88007fa86d30 RBX: 8800bba16000 RCX:
0002
[9.007227] RDX: RSI: 88007fa86cc0 RDI:
8800bba16088
[9.007227] RBP: 88013ab8bc48 R08: 88007f09e09c R09:
88013b001800
[9.007227] R10: 88007fa86cc0 R11: R12:
88007fa86cc0
[9.007227] R13: 8800bba16088 R14: 8800bb9f7d88 R15:
88013a52f010
[9.007227] FS: () GS:88013fc0()
knlGS:
[9.007227] CS: 0010 DS: ES: CR0: 80050033
[9.007227] CR2: 0008 CR3: 00013a53 CR4:
001406f0
[9.007227] Stack:
[9.007227] 88007fa86cc0 88013a52f000 8800bb9f7d88
88013ab8bc58
[9.007227] c01d153b 88013ab8bc80 c01d3d37
88013a52f000
[9.007227] 8800bb9f7d88 88013ab8bca0
c01d010d
[9.007227] Call Trace:
[9.007227] [] nfs_file_set_open_context+0x2b/0x30 [nfs]
[9.007227] [] nfs_open+0x37/0x60 [nfs]
[9.007227] [] nfs_file_open+0x4d/0x70 [nfs]
[9.007227] [] do_dentry_open+0x1ff/0x310
[9.007227] [] ? nfs_file_fsync+0x130/0x130 [nfs]
[9.007227] [] vfs_open+0x56/0x60
[9.007227] [] path_openat+0x1b7/0x1360
[9.007227] [] do_filp_open+0x91/0x100
[9.007227] [] ? __alloc_fd+0xc8/0x190
[9.007227] [] do_sys_open+0x13e/0x2a0
[9.007227] [] ? __put_cred+0x3d/0x50
[9.007227] [] ? SyS_access+0x1e8/0x230
[9.007227] [] SyS_open+0x1e/0x20
[9.007227] [] entry_SYSCALL_64_fastpath+0x16/0x71
[9.007227] Code: 54 53 48 8b 47 40 49 89 fc 48 8b 58 30 4c 8d ab 88 00 00
00 4c 89 ef e8 98 37 65 c1 48 8b 93 60 ff ff ff 49 8d 44 24 70 4c 89 ef <48> 89
42 08 49 89 54 24 70 48 8d 93 60 ff ff ff 49 89 54 24 78
[9.007227] RIP []
nfs_inode_attach_open_context+0x37/0x70 [nfs]
[9.007227] RSP
[9.007227] CR2: 0008
[9.056135] ---[ end trace 4bf38e0df912649a ]---
[9.057055] BUG: unable to handle kernel NULL pointer dereference at
0158
[9.058345] IP: [] __put_nfs_open_context+0xa0/0x100
[nfs]
[9.059479] PGD 0
[9.059823] Oops: [#2] SMP
[Kernel-packages] [Bug 1542939] Re: system freeze after vt switching
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1542939 Title: system freeze after vt switching Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-lts-xenial source package in Xenial: In Progress Status in Fedora: Unknown Bug description: I'm trying to use the ctrl+alt+1 to switch to a terminal - ok, after switching back by ctrl+alt+7 the system freeze ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-3-generic 4.4.0-3.17 ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1 Uname: Linux 4.4.0-3-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stinger1644 F pulseaudio Date: Sun Feb 7 22:27:42 2016 HibernationDevice: RESUME=UUID=888e93f3-1a7d-4bf8-a00d-cea6a759d03a InstallationDate: Installed on 2015-11-12 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151112) Lsusb: Bus 002 Device 003: ID 24ae:2000 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. P53E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-3-generic root=UUID=9ad09333-ac7d-4b10-99a0-1e598daa4753 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-3-generic N/A linux-backports-modules-4.4.0-3-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P53E.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP53E.209:bd03/15/2012:svnASUSTeKComputerInc.:pnP53E:pvr1.0:rvnASUSTeKComputerInc.:rnP53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1542939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] [NEW] When using overlayfs with kernel 4.4, some files cannot be deleted.
Public bug reported:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: overlayfs
** Description changed:
#!/bin/bash
- #
--
+ # -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
- # The bug can be reproduced in an x86_64 virtual-machine; 32-bit has not been
tested.
+ # The bug can be reproduced in an x86_64 virtual-machine;
+ # 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
- # "rm: cannot remove ‘mnt_ovl/sub/sub.txt’: Value too large for defined
data type"
+ # "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
+ #Value too large for defined data type"
#
- # The script depends upon lxc-usernsexec (part of the lxc1 package) to create
a user-namespace.
+ # The script depends upon lxc-usernsexec (part of the lxc1 package) to
+ # create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
- #
--
+ #
cleanup()
{
-[[ -d "$storedir" ]] || exit 1
-cd "$storedir" || exit 1
-[[ -d "$tmpdir" ]] || exit 1
-lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
+ [[ -d "$storedir" ]] || exit 1
+ cd "$storedir" || exit 1
+ [[ -d "$tmpdir" ]] || exit 1
+ lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
-set -e
-cd "$tmpdir"
+ set -e
+ cd "$tmpdir"
-# create tmpfs
-mkdir mnt_tmpfs
-mount -t tmpfs tmpfs mnt_tmpfs
+ # create tmpfs
+ mkdir mnt_tmpfs
+ mount -t tmpfs tmpfs mnt_tmpfs
-# create upperdir and workdir for overlay
-mkdir mnt_tmpfs/{upper,work}
+ # create upperdir and workdir for overlay
+ mkdir mnt_tmpfs/{upper,work}
-# mount overlay
-mkdir mnt_ovl
-mount -t overlay \
--o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work overlay
mnt_ovl
+ # mount overlay
+ mkdir mnt_ovl
+ mount -t overlay \
+ -o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
+overlay mnt_ovl
-echo 'overlay directory listing'
-ls -RF mnt_ovl
-echo ''
+ echo 'overlay directory listing'
+ ls -RF mnt_ovl
+ echo ''
-set -x
-rm
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Aug 26 15:09 seq
+ crw-rw 1 root audio 116, 33 Aug 26 15:09 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=vt102
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic
root=UUID=78cee363-0cf0-46ce-bd06-d5601344c627 ro console=tty1 console=ttyS0
+ ProcVersionSignature: User Name 4.4.0-34.53~14.04.1-generic 4.4.15
+ RelatedPackageVersions:
+ linux-restricted-modules-4.4.0-34-generic N/A
+ linux-backports-modules-4.4.0-34-generic N/A
+ linux-firmwareN/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty uec-images
+ Uname: Linux 4.4.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 01/01/2011
+ dmi.bios.vendor: Bochs
+ dmi.bios.version: Bochs
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Bochs
+ dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-trusty
+ dmi.sys.vendor: QEMU
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728459/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot
[Kernel-packages] [Bug 1617388] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728467/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] UdevLog.txt
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728466/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728463/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728465/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728464/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728460/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728461/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1617388/+attachment/4728462/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
More Apport-Collect data:
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Aug 26 15:09 seq
crw-rw 1 root audio 116, 33 Aug 26 15:09 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic
root=UUID=78cee363-0cf0-46ce-bd06-d5601344c627 ro console=tty1 console=ttyS0
ProcVersionSignature: User Name 4.4.0-34.53~14.04.1-generic 4.4.15
RelatedPackageVersions:
linux-restricted-modules-4.4.0-34-generic N/A
linux-backports-modules-4.4.0-34-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images
Uname: Linux 4.4.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
** Description changed:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
-overlay mnt_ovl
+ overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
- ---
- AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Aug 26 15:09 seq
- crw-rw 1 root audio 116, 33 Aug 26 15:09 timer
- AplayDevices: Error: [Errno 2] No such file or directory
- ApportVersion: 2.14.1-0ubuntu3.21
- Architecture: amd64
- ArecordDevices: Error: [Errno 2] No such file or directory
- AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
- CRDA: Error: [Errno 2] No such file or directory
- DistroRelease: Ubuntu 14.04
- IwConfig: Error: [Errno 2] No such file or directory
- Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
- MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
- Package: linux (not installed)
- PciMultimedia:
-
- ProcEnviron:
- TERM=vt102
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
- ProcFB:
-
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic
root=UUID=78cee363-0cf0-46ce-bd06-d5601344c627 ro console=tty1 console=ttyS0
- ProcVersionSig
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
** Description changed:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
+
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
git bisect of the ubuntu-xenial tree:
last good commit: 0e9c9b5 UBUNTU: SAUCE: cred: Reject inodes with invalid ids
in set_create_file_as()
first bad commit: eac15dc UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't
map into s_user_ns
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
For reference, here is the bad commit:
commit eac15dc
Author: Seth Forshee
Date: Wed Nov 19 11:00:56 2014 -0600
UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't map into s_user_ns
Add checks to inode_change_ok to verify that uid and gid changes
will map into the superblock's user namespace. If they do not
fail with -EOVERFLOW. This cannot be overriden with ATTR_FORCE.
Signed-off-by: Seth Forshee
Acked-by: Serge Hallyn
Signed-off-by: Tim Gardner
diff --git a/fs/attr.c b/fs/attr.c
index 6530ced..55b46e3 100644
--- a/fs/attr.c
+++ b/fs/attr.c
@@ -42,6 +42,17 @@ int inode_change_ok(const struct inode *inode, struct iattr
*attr)
return error;
}
+ /*
+* Verify that uid/gid changes are valid in the target namespace
+* of the superblock. This cannot be overriden using ATTR_FORCE.
+*/
+ if (ia_valid & ATTR_UID &&
+ from_kuid(inode->i_sb->s_user_ns, attr->ia_uid) == (uid_t)-1)
+ return -EOVERFLOW;
+ if (ia_valid & ATTR_GID &&
+ from_kgid(inode->i_sb->s_user_ns, attr->ia_gid) == (gid_t)-1)
+ return -EOVERFLOW;
+
/* If force is set do it anyway. */
if (ia_valid & ATTR_FORCE)
return 0;
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
** Tags added: bisect-done kernel-bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Confirmed
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
Thank you for the detailed explanation.
Since the underlying problem is that overlayfs is not (yet very)
namespace aware, this issue may be intractable.
Naive question regarding copy-up: Do the files in the upperdir and
lowerdir need to have the same owner? If not, could copy-up be amended
so that it behaves similarly to the copying of a root-owned file by a
non-root user? Ie the ownership of the file in the upperdir could
change to that of the user doing the copying/deleting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Triaged
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
Real-world-use case: running ephemeral, containerized instances of an
app:
There may be multiple instances of the app, each running
in a separate ephemeral container with a unique uid_map.
The app's configuration directory is permanently stored on the host,
and is mounted in each container using overlayfs.
Permission for each container to access the configuration directory is granted
via
either 'chmod a+rwX' or 'setfacl -m -u:container_uid:rwX'.
In certain situations it is desirable for the upper layer of overlayfs to be
tmpfs:
-read-only host filesystem
-the host's disk is writeable but very slow (eg thumb-drives, nfs)
-the host filesystem is btrfs
(cannot be used as the upper layer with the 4.4 kernel. fixed in 4.7)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Triaged
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
> First, starting in xenial the tmpfs mount isn't going to allow any
inodes to be created in it that > are not mapped into the user
namespace.
Is this specific to tmpfs? I was unable to locate the relevant
code/commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Triaged
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
Question (related to UBUNTU: SAUCE: fs: Refuse uid/gid changes which don't map
into s_user_ns)
---
When an overlayfs is mounted inside a user-namespace, should it permit
the creation of inodes in the upper layer with uids that are outside the
user-namespace?
My Tentative Answer
---
(TLDR; yes)
If a directory D is granted world-write permissions (in the initial namespace)
via 'chmod -R a+rwX', then any user is permitted to edit or delete files in D,
even if the files and D are owned by root.
If we subsequently enter a user-namespace, then we are still permitted
to edit files in D.
But if we enter a user-namespace and subsequently utilize D as the lower
layer of an overlayfs, then editing files in D necessitates the creation
of files in the upper layer with uids which are outside the user
namespace.
While restriciting the permissible range of uids in the upper layer may
well enhance security, it also limits the utility of overlayfs.
overlayfs will sometimes deny permissions which were granted in the
initial namespace. overlayfs will remain useful for mounting a rootfs
(since all uids are within the user-namespace), but not for mounting
directories onto the rootfs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Triaged
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1617388] Re: When using overlayfs with kernel 4.4, some files cannot be deleted.
> This also means that a kuid outside of the range 10-165535
> is literally meaningless with respect to that mount - the kernel
> has no way to map it to an id valid in the filesystem.
> That is the real reason for the patch.
That is a compelling point. mounts inside a user-namespace are only
well-defined if every file's uid lies within the user-namespace.
I wish I had realised that prior to filing the bug report, and am
now happy to close it as not-a-bug (-: Thank you for your
highly informative replies.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1617388
Title:
When using overlayfs with kernel 4.4, some files cannot be deleted.
Status in linux package in Ubuntu:
Invalid
Bug description:
#!/bin/bash
# -
# This script exhibits a bug in overlayfs in kernel 4.4.
# The bug is not present in kernel 4.2.
# The bug can be reproduced in an x86_64 virtual-machine;
# 32-bit has not been tested.
#
# With kernel 4.2, the script output ends with:
# "script completed without encountering a kernel bug"
#
# With kernel 4.4, the script output ends with:
# "rm: cannot remove ‘mnt_ovl/sub/sub.txt’:
#Value too large for defined data type"
#
# The script depends upon lxc-usernsexec (part of the lxc1 package) to
# create a user-namespace.
#
# The script should be run as a normal user (not root), in a directory where
# the user has write-permission:
# ./script
#
cleanup()
{
[[ -d "$storedir" ]] || exit 1
cd "$storedir" || exit 1
[[ -d "$tmpdir" ]] || exit 1
lxc-usernsexec -m b:0:1000:1 -m b:10:10:1 -- rm -rf "$tmpdir"
}
trap cleanup EXIT
set -e
storedir="$(pwd)"
# create tmpdir
tmpdir="$(mktemp -d --tmpdir=.)"
cd "$tmpdir"
# create lowerdir for overlay
mkdir -p lower/sub
touch lower/lower.txt lower/sub/sub.txt
cd ..
chmod -R a+rwX "$tmpdir"
# run a script in a user namepace
lxc-usernsexec -m b:0:10:65534 -- bash << EOF
set -e
cd "$tmpdir"
# create tmpfs
mkdir mnt_tmpfs
mount -t tmpfs tmpfs mnt_tmpfs
# create upperdir and workdir for overlay
mkdir mnt_tmpfs/{upper,work}
# mount overlay
mkdir mnt_ovl
mount -t overlay \
-o lowerdir=lower,upperdir=mnt_tmpfs/upper,workdir=mnt_tmpfs/work \
overlay mnt_ovl
echo 'overlay directory listing'
ls -RF mnt_ovl
echo ''
set -x
rm mnt_ovl/lower.txt# always succeeds
rm mnt_ovl/sub/sub.txt # fails with kernel 4.4+
set +x
echo 'script completed without encountering a kernel bug'
EOF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1617388/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479468] Re: OverlayFS: Wrong mnt_id and path reported in /proc
This bug also affects the 3.13 kernel in Ubuntu Trusty.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1479468
Title:
OverlayFS: Wrong mnt_id and path reported in /proc
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Vivid:
Fix Released
Bug description:
SRU Justification:
[Impact]
I am running Ubuntu Vivid (3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16
17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). There are two
issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
[Fix]
These problems can be easily reproduced with the shell script below.
Fortunately, both problems have been fixed in the upstream's master
branch of the kernel via the following commits:
torvalds 4.0: 155e35d4d VFS: Introduce inode-getting helpers for
layered/unioned fs environments (this is already in ubuntu-vivid)
torvalds 4.0: df1a085af VFS: Add a fallthrough flag for marking virtual
dentries
torvalds 4.2-rc2: f25801ee4 overlay: Call ovl_drop_write() earlier in
ovl_dentry_open()
torvalds 4.2-rc2: 4bacc9c92 overlayfs: Make f_path always point to the
overlay and f_inode to the underlay
torvalds 4.2-rc2: 9391dd00d fix a braino in ovl_d_select_inode()
(The commit df1a085af may technically not be needed but it prevents a
conflict when applying 4bacc9c92.)
[Test Case]
Simple script to reproduce the problem:
#!/bin/bash
set -eu
ERROR=0
setup() {
setup_mount
start_python > /dev/null 2>&1 &
BASH_PID=$!
PYTHON_PID=$(ps -C python | awk '/python/ { print $1 }')
sleep 1
}
setup_mount() {
mkdir overlay_test
cd overlay_test
mkdir a b c z
sudo mount -t overlay -o lowerdir=a,upperdir=b,workdir=c overlayfs z
}
start_python() {
python << EOF
import time
fd = open("z/file", "w")
time.sleep(10)
EOF
}
check_path() {
WD=$(pwd)
if ! ls -l /proc/$PYTHON_PID/fd | grep -qw "$WD/z/file"; then
ERROR=1
echo "ERROR! expected $WD/z/file"
set -x
ls -l /proc/$PYTHON_PID/fd
set +x
fi
}
check_mnt_id() {
FDINFO_MNT_ID=$(awk '/mnt_id:/ { print $2 }' /proc/$PYTHON_PID/fdinfo/3)
MOUNTINFO_MNT_ID=$(awk '/overlayfs/ { print $1 }' /proc/self/mountinfo)
if [[ $FDINFO_MNT_ID -ne $MOUNTINFO_MNT_ID ]]; then
ERROR=1
echo "ERROR! mnt_id $FDINFO_MNT_ID not in /proc/self/mountinfo"
set -x
cat /proc/$PYTHON_PID/fdinfo/3
cat /proc/self/mountinfo
set +x
fi
}
finish() {
kill -INT $PYTHON_PID > /dev/null 2>&1
sudo umount z
cd $ORIG_WD
rm -rf overlay_test
}
main() {
ORIG_WD=$(pwd)
setup
check_path
check_mnt_id
finish
[[ $ERROR -eq 0 ]] && echo "OverlayFS looks good."
}
main
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479468/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] [NEW] OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Public bug reported:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the 3.13
kernel, possibly because it contains an older version of overlayfs.
These issues are now adversely affecting some versions of lxc when used
in conjunction with the 3.13 kernel, because lxc has recently been
patched to pass /proc//fd/ to the mount syscall. This change
to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The following versions of lxc are affected:
repository lxc version
impact
--
trusty 1.0.7-0ubuntu0.7
not affectd
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
affected
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-stop-nagging overlayfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
New
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The following versions of lxc are affected:
repository lxc version
impact
--
trusty 1.0.7-0ubuntu0.7
not affectd
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
affected
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/s
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The following versions of lxc are affected:
repository lxc version
impact
--
trusty 1.0.7-0ubuntu0.7
not affectd
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
affected
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
affected
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
- 1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
+ 1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
- 2. /proc//fd/ shows incorrect path for the symlink target
+ 2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the 3.13
kernel, possibly because it contains an older version of overlayfs.
These issues are now adversely affecting some versions of lxc when used
in conjunction with the 3.13 kernel, because lxc has recently been
patched to pass /proc//fd/ to the mount syscall. This change
to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
- The following versions of lxc are affected:
+ The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
+ is not affected. The following versions of lxc are affected:
- repository lxc version
impact
-
--
- trusty 1.0.7-0ubuntu0.7
not affectd
- ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
affected
- ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
affected
- ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
affected
+ repository lxc version
+
+ ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
+ ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
+ ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~
[Kernel-packages] [Bug 1507463] UdevLog.txt
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499895/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffile..e
[Kernel-packages] [Bug 1507463] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499890/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.con
[Kernel-packages] [Bug 1507463] lxc-net.default.txt
apport information
** Attachment added: "lxc-net.default.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499897/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
m
[Kernel-packages] [Bug 1507463] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499892/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.con
[Kernel-packages] [Bug 1507463] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499894/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffile..etc.
[Kernel-packages] [Bug 1507463] KernLog.txt
apport information
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499888/+files/KernLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffile..e
[Kernel-packages] [Bug 1507463] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499891/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mti
[Kernel-packages] [Bug 1507463] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499896/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conff
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
apport information
** Tags added: apparmor apport-collected third-party-packages uec-images
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the 3.13
kernel, possibly because it contains an older version of overlayfs.
These issues are now adversely affecting some versions of lxc when used
in conjunction with the 3.13 kernel, because lxc has recently been
patched to pass /proc//fd/ to the mount syscall. This change
to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
+ crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.15
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
+ PackageArchitecture: amd64
+ PciMultimedia:
+
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
+ ProcEnviron:
+ TERM=vt102
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
+ ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty uec-images third-party-packages trusty uec-images apparmor
+ Uname: Linux 3.13.0-65-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
+ _MarkForUpload: True
+ defaults.conf:
+ lxc.network.type = empty
+ #lxc.network.link = lxcbr0
+ #lxc.network.flags = up
+ #lxc.network.hwaddr = 00:16:3e:xx:xx:xx
+ dmi.bios.date: 01/01/2011
+ dmi.bios.vendor: Bochs
+ dmi.bios.version: Bochs
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Bochs
+ dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-trusty
+ dmi.sys.vendor: QEMU
+ modified.conffile..etc.default.lxc: [modified]
+ modified.conffile..etc.lxc.default.conf: [modified]
+ mtime.conffile..etc.default.lxc: 2015-10-14T06:30:28.860979
+ mtime.conffile..etc.lxc.default.conf: 2015-10-14T06:42:05.568979
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499885/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
[Kernel-packages] [Bug 1507463] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499889/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffile..etc.de
[Kernel-packages] [Bug 1507463] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499886/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.c
[Kernel-packages] [Bug 1507463] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499887/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.c
[Kernel-packages] [Bug 1507463] lxc.default.txt
apport information
** Attachment added: "lxc.default.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499898/+files/lxc.default.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.con
[Kernel-packages] [Bug 1507463] RelatedPackageVersions.txt
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499893/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf:
[Kernel-packages] [Bug 1507463] lxcsyslog.txt
apport information
** Attachment added: "lxcsyslog.txt"
https://bugs.launchpad.net/bugs/1507463/+attachment/4499923/+files/lxcsyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
New
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
PackageArchitecture: amd64
PciMultimedia:
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images third-party-packages trusty uec-images apparmor
Uname: Linux 3.13.0-65-generic x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_MarkForUpload: True
defaults.conf:
lxc.network.type = empty
#lxc.network.link = lxcbr0
#lxc.network.flags = up
#lxc.network.hwaddr = 00:16:3e:xx:xx:xx
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
modified.conffile..etc.default.lxc: [modified]
modified.conffile..etc.lxc.default.conf: [modified]
mtime.conffil
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** Description changed:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2
22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the 3.13
kernel, possibly because it contains an older version of overlayfs.
These issues are now adversely affecting some versions of lxc when used
in conjunction with the 3.13 kernel, because lxc has recently been
patched to pass /proc//fd/ to the mount syscall. This change
to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
- ---
- AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Oct 19 07:31 seq
- crw-rw 1 root audio 116, 33 Oct 19 07:31 timer
- AplayDevices: Error: [Errno 2] No such file or directory
- ApportVersion: 2.14.1-0ubuntu3.15
- Architecture: amd64
- ArecordDevices: Error: [Errno 2] No such file or directory
- AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
- CRDA: Error: [Errno 2] No such file or directory
- DistroRelease: Ubuntu 14.04
- IwConfig: Error: [Errno 2] No such file or directory
- Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
- MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
- Package: lxc 1.1.3+master~20151012-0541-0ubuntu1~trusty [origin:
LP-PPA-ubuntu-lxc-daily]
- PackageArchitecture: amd64
- PciMultimedia:
-
- ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
- ProcEnviron:
- TERM=vt102
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
- ProcFB:
-
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic
root=UUID=0ddfd60f-0567-41c7-a1a0-9b562f0b4cf9 ro console=tty1 console=ttyS0
- ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
- RfKill: Error: [Errno 2] No such file or directory
- Tags: trusty uec-images third-party-packages trusty uec-images apparmor
- Uname: Linux 3.13.0-65-generic x86_64
- UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
- _MarkForUpload: True
- defaults.conf:
- lxc.network.type = empty
- #lxc.network.link = lxcbr0
- #lxc.network.flags = up
- #lxc.network.hwaddr = 00:16:3e:xx:xx:xx
- dmi.bios.date: 01/01/2011
- dmi.bios.vendor: Bochs
- dmi.bios.version: Bochs
- dmi.chassis.type: 1
- dmi.chassis.vendor: Bochs
- dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
- dmi.product.name: Standard PC (i440FX + PIIX, 1996)
- dmi.product.version: pc-i440fx-trusty
- dmi.sys.vendor: QEMU
- modified.conffile..etc.default.lxc: [modified]
- modified.conffile..etc.lxc.default.conf: [modified]
- mtime.conffile..etc.default.lxc: 2015-10-14T06:30:28.860979
- mtime.conffile..etc.lxc.default.conf: 2015-10-14T06:42:05.568979
** Tags removed: apparmor apport-collected third-party-packages
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong
[Kernel-packages] [Bug 1479468] Re: OverlayFS: Wrong mnt_id and path reported in /proc
Bug #1507463 has been filed for the 3.13 kernel in Ubuntu Trusty, which
is also affected and has not yet been patched.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1479468
Title:
OverlayFS: Wrong mnt_id and path reported in /proc
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Vivid:
Fix Released
Bug description:
SRU Justification:
[Impact]
I am running Ubuntu Vivid (3.19.0-22-generic #22-Ubuntu SMP Tue Jun 16
17:15:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). There are two
issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
[Fix]
These problems can be easily reproduced with the shell script below.
Fortunately, both problems have been fixed in the upstream's master
branch of the kernel via the following commits:
torvalds 4.0: 155e35d4d VFS: Introduce inode-getting helpers for
layered/unioned fs environments (this is already in ubuntu-vivid)
torvalds 4.0: df1a085af VFS: Add a fallthrough flag for marking virtual
dentries
torvalds 4.2-rc2: f25801ee4 overlay: Call ovl_drop_write() earlier in
ovl_dentry_open()
torvalds 4.2-rc2: 4bacc9c92 overlayfs: Make f_path always point to the
overlay and f_inode to the underlay
torvalds 4.2-rc2: 9391dd00d fix a braino in ovl_d_select_inode()
(The commit df1a085af may technically not be needed but it prevents a
conflict when applying 4bacc9c92.)
[Test Case]
Simple script to reproduce the problem:
#!/bin/bash
set -eu
ERROR=0
setup() {
setup_mount
start_python > /dev/null 2>&1 &
BASH_PID=$!
PYTHON_PID=$(ps -C python | awk '/python/ { print $1 }')
sleep 1
}
setup_mount() {
mkdir overlay_test
cd overlay_test
mkdir a b c z
sudo mount -t overlay -o lowerdir=a,upperdir=b,workdir=c overlayfs z
}
start_python() {
python << EOF
import time
fd = open("z/file", "w")
time.sleep(10)
EOF
}
check_path() {
WD=$(pwd)
if ! ls -l /proc/$PYTHON_PID/fd | grep -qw "$WD/z/file"; then
ERROR=1
echo "ERROR! expected $WD/z/file"
set -x
ls -l /proc/$PYTHON_PID/fd
set +x
fi
}
check_mnt_id() {
FDINFO_MNT_ID=$(awk '/mnt_id:/ { print $2 }' /proc/$PYTHON_PID/fdinfo/3)
MOUNTINFO_MNT_ID=$(awk '/overlayfs/ { print $1 }' /proc/self/mountinfo)
if [[ $FDINFO_MNT_ID -ne $MOUNTINFO_MNT_ID ]]; then
ERROR=1
echo "ERROR! mnt_id $FDINFO_MNT_ID not in /proc/self/mountinfo"
set -x
cat /proc/$PYTHON_PID/fdinfo/3
cat /proc/self/mountinfo
set +x
fi
}
finish() {
kill -INT $PYTHON_PID > /dev/null 2>&1
sudo umount z
cd $ORIG_WD
rm -rf overlay_test
}
main() {
ORIG_WD=$(pwd)
setup
check_path
check_mnt_id
finish
[[ $ERROR -eq 0 ]] && echo "OverlayFS looks good."
}
main
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479468/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
I retested using lxc-1.1.4 from the lxc-stable ppa
(https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable) which I
added to a fresh vm image from the daily-builds, https://cloud-
images.ubuntu.com/trusty/current.
"lxc-start -n trusty_overlay" fails as before, with the same error
message,
ERRORlxc_utils - utils.c:safe_mount:1641 - Permission denied - Failed to
mount /home/ubuntu/test.txt onto
/usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt
ERRORlxc_conf - conf.c:mount_entry:1731 - Permission denied - failed to
mount '/home/ubuntu/test.txt' on
'/usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt'
ERRORlxc_conf - conf.c:lxc_setup:3745 - failed to setup the mount entries
for 'trusty_overlay'
Chris, it would be of interest to see whether you can reproduce the
underlying kernel bug using this script,
#!/bin/bash
fatal() { echo "error: $@"; exit 1; }
echo -e "testing for overlayfs kernel bug in kernels <= 3.17.";
echo -e "(This script does not work for the newer version of overlayfs in
kernels 3.18+)";
mkdir test_dir|| fatal "mkdir test_dir";
sudo mount -t tmpfs none test_dir || fatal "mount tmpfs";
cd test_dir;
mkdir lowerdir upperdir overlayfs;
sudo mount -t overlayfs -o lowerdir=lowerdir,upperdir=upperdir none overlayfs
|| fatal "mount overlayfs";
exec 6> file_tmpfs.txt;
exec 7> lowerdir/file_lowerdir.txt;
exec 8> upperdir/file_upperdir.txt;
exec 9> overlayfs/file_overlayfs.txt;
echo -e "\ncontents of /proc/$BASHPID/fd/ . A broken symbolic link to
file_overlayfs.txt indicates a kernel bug";
echo
"";
file /proc/$BASHPID/fd/[6-9];
# cleanup
exec 9>&-;
exec 8>&-;
exec 7>&-;
exec 6>&-;
sudo umount overlayfs;
cd ..;
sudo umount test_dir && rmdir test_dir;
#--end of script
Running the script as root, sudo ./script, I get the following output,
testing for overlayfs kernel bug in kernels <= 3.17.
(This script does not work for the newer version of overlayfs in kernels
3.18+)
contents of /proc/1916/fd/ . A broken symbolic link to file_overlayfs.txt
indicates a kernel bug
/proc/1916/fd/6: symbolic link to `/home/ubuntu/test_dir/file_tmpfs.txt'
/proc/1916/fd/7: symbolic link to
`/home/ubuntu/test_dir/lowerdir/file_lowerdir.txt'
/proc/1916/fd/8: symbolic link to
`/home/ubuntu/test_dir/upperdir/file_upperdir.txt'
/proc/1916/fd/9: broken symbolic link to `/file_overlayfs.txt'
It seems that the kernel bug is causing fd 9 to point to
/file_overlayfs.txt, when it should point to
/home/ubuntu/test_dir/overlayfs/file_overlayfs.txt .
The lxc commit which introduced safe_mount(), which passes fd's as
arguments to mount() is,
CVE-2015-1335: Protect container mounts against symlinks
https://github.com/lxc/lxc/commit/6de26af93d3dd87c8b21a42fdf20f30fa1c1948d
Here is the relevant part of the commit, which creates a file descriptor
and passes it to mount().
+ destfd = open_without_symlink(dest, rootfs);
+ if (destfd < 0) {
+ if (srcfd != -1)
+ close(srcfd);
+ return destfd;
+ }
+
+ ret = snprintf(destbuf, 50, "/proc/self/fd/%d", destfd);
+ if (ret < 0 || ret > 50) {
+ if (srcfd != -1)
+ close(srcfd);
+ close(destfd);
+ ERROR("Out of memory");
+ return -EINVAL;
+ }
+
+ ret = mount(mntsrc, destbuf, fstype, flags, data);
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1335
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
Incomplete
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Chris, it would be of interest to see whether you can reproduce the
underlying kernel bug using this script,
#!/bin/bash
fatal() { echo "error: $@"; exit 1; }
echo -e "testing for overlayfs kernel bug in kernels <= 3.17.";
echo -e "(This script does not work for the newer version of overlayfs in
kernels 3.18+)";
mkdir test_dir || fatal "mkdir test_dir";
sudo mount -t tmpfs none test_dir || fatal "mount tmpfs";
cd test_dir;
mkdir lowerdir upperdir overlayfs;
sudo mount -t overlayfs -o lowerdir=lowerdir,upperdir=upperdir none overlayfs
|| fatal "mount overlayfs";
exec 6> file_tmpfs.txt;
exec 7> lowerdir/file_lowerdir.txt;
exec 8> upperdir/file_upperdir.txt;
exec 9> overlayfs/file_overlayfs.txt;
echo -e "\ncontents of /proc/$BASHPID/fd/ . A broken symbolic link to
file_overlayfs.txt indicates a kernel bug";
echo
"";
file /proc/$BASHPID/fd/[6-9];
# cleanup
exec 9>&-;
exec 8>&-;
exec 7>&-;
exec 6>&-;
sudo umount overlayfs;
cd ..;
sudo umount test_dir && rmdir test_dir;
#--end of script
Running the script as root, sudo ./script, I get the following output,
testing for overlayfs kernel bug in kernels <= 3.17.
(This script does not work for the newer version of overlayfs in kernels
3.18+)
contents of /proc/1916/fd/ . A broken symbolic link to file_overlayfs.txt
indicates a kernel bug
/proc/1916/fd/6: symbolic link to `/home/ubuntu/test_dir/file_tmpfs.txt'
/proc/1916/fd/7: symbolic link to
`/home/ubuntu/test_dir/lowerdir/file_lowerdir.txt'
/proc/1916/fd/8: symbolic link to
`/home/ubuntu/test_dir/upperdir/file_upperdir.txt'
/proc/1916/fd/9: broken symbolic link to `/file_overlayfs.txt'
It seems that the kernel bug is causing fd 9 to point to
/file_overlayfs.txt, when it should point to
/home/ubuntu/test_dir/overlayfs/file_overlayfs.txt .
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
Incomplete
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
I retested using lxc-1.1.4 from the lxc-stable ppa
(https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-stable), which I
added to a fresh VM image from the Trusty daily-builds, https://cloud-
images.ubuntu.com/trusty/current.
"lxc-start -n trusty_overlay" fails as before, with the same error
message,
ERROR lxc_utils - utils.c:safe_mount:1641 - Permission denied - Failed to mount
/home/ubuntu/test.txt onto /usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt
ERROR lxc_conf - conf.c:mount_entry:1731 - Permission denied - failed to mount
'/home/ubuntu/test.txt' on '/usr/lib/x86_64-linux-gnu/lxc/home/ubuntu/test.txt'
ERROR lxc_conf - conf.c:lxc_setup:3745 - failed to setup the mount entries for
'trusty_overlay'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
Incomplete
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
The following lxc commit introduced safe_mount(), which passes fd's as
arguments to mount(),
CVE-2015-1335: Protect container mounts against symlinks
https://github.com/lxc/lxc/commit/6de26af93d3dd87c8b21a42fdf20f30fa1c1948d
Here is the relevant part of the commit, which creates a file descriptor
and passes it to mount().
+ destfd = open_without_symlink(dest, rootfs);
+ if (destfd < 0) {
+ if (srcfd != -1)
+ close(srcfd);
+ return destfd;
+ }
+
+ ret = snprintf(destbuf, 50, "/proc/self/fd/%d", destfd);
+ if (ret < 0 || ret > 50) {
+ if (srcfd != -1)
+ close(srcfd);
+ close(destfd);
+ ERROR("Out of memory");
+ return -EINVAL;
+ }
+
+ ret = mount(mntsrc, destbuf, fstype, flags, data);
The strace of mount() shows,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Incomplete
Status in lxc package in Ubuntu:
Incomplete
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Confirmed
Status in lxc package in Ubuntu:
Confirmed
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Related bug #1347746 : Overlayfs breaks /proc/self/exe link
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Confirmed
Status in lxc package in Ubuntu:
Confirmed
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
This bug does still affect lxc on Ubuntu Trusty when using the 3.13
kernel in conjunction with the latest daily-build of lxc,
1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa,
https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily).
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Confirmed
Status in lxc package in Ubuntu:
Confirmed
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
This bug does still affect lxc when using kernel 3.18 or above in conjunction with the latest daily-build of lxc, 1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa, https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily). ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
This bug does still affect lxc (as per comment #5) when using kernel 3.18 or above in conjunction with the latest daily-build of lxc, 1.1.5+master~20151110-0623-0ubuntu1~trusty (from the lxc-daily ppa, https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/daily). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
@Serge, Thanks for the clarification; I'll revert the status to un-marked. ** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Confirmed Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
** No longer affects: lxc (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux package in Ubuntu:
Confirmed
Bug description:
I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).
There are two issues in OverlayFS as follows:
1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
/proc//mountinfo)
2. /proc//fd/ shows incorrect path for the symlink target
These issues were previously reported and patched for the Ubuntu Vivid
kernel (3.19) in bug #1479468, but the patch was not applied to the
3.13 kernel, possibly because it contains an older version of
overlayfs.
These issues are now adversely affecting some versions of lxc when
used in conjunction with the 3.13 kernel, because lxc has recently
been patched to pass /proc//fd/ to the mount syscall. This
change to lxc was made in response to cve-2015-1335; see bug #1476662.
The kernel issues cause some overlayfs-backed containers to fail to
start, with error message,
strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)
The mount fails because /proc/self/fd/16, which should point to a file
in overlayfs, has an invalid value.
The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
is not affected. The following versions of lxc are affected:
repository lxc version
ppa:ubuntu-lxc/lxc-git-stable-1.0 1.0.7+stable~20151014-2143-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-stable-1.1 1.1.3+stable~20151007-2301-0ubuntu1~trusty
ppa:ubuntu-lxc/lxc-git-master 1.1.3+master~20151012-0541-0ubuntu1~trusty
To reproduce the lxc failure-to-start issue:
# Install the 3.13 kernel and also an affected version of lxc.
lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
touch $HOME/test.txt;
echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
lxc-clone -s -B overlayfs trusty trusty_overlay;
lxc-start -n trusty_overlay; # fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507463/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] [NEW] rm -r * fails to delete directories when using overlayfs in a user-namespace
Public bug reported: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel. The bug does not occur with the default 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the underlying filesystem is tmpfs or ext4. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: overlayfs ** Attachment added: "script to reproduce the bug" https://bugs.launchpad.net/bugs/1480411/+attachment/4437088/+files/overlayfs-bug.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: New Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel. The bug does not occur with the default 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the underlying filesystem is tmpfs or ext4. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** Description changed: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, -mount -n -t overlay overlay -o + mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, -rm -r mntpt/foo + rm -r mntpt/foo fails with error message, -"rm: cannot remove ‘mntpt/foo’: Operation not permitted" + "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, - unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation + unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel. - The bug does not occur with the default 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) - - The bug occurs regardless of whether the underlying filesystem is tmpfs or ext4. + The bug does not occur with the default 3.13 kernel. The bug occurs for + any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow + unprivileged mounts" is added. (The patch is at, + http://kernel.ubuntu.com/git/ubuntu/ubuntu- + vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) + + The bug occurs regardless of whether the underlying filesystem is tmpfs + or ext4. + + The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a + virtual machine (qemu-kvm). The host is ubuntu 14.04 with the linux- + generic-lts-vivid kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 ** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Triaged Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel. The bug does not occur with the default 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the underlying filesystem is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-kvm). The host is ubuntu 14.04 with the linux- generic-lts-vivid kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** Description changed: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid - kernel. + kernel (3.19). - The bug does not occur with the default 3.13 kernel. The bug occurs for - any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow - unprivileged mounts" is added. (The patch is at, + The bug does not occur on ubuntu 14.04.2 with the default linux-generic + 3.13 kernel. + + The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, + "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) - The bug occurs regardless of whether the underlying filesystem is tmpfs - or ext4. + The bug occurs regardless of whether the filesystem underlying overlayfs + is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a - virtual machine (qemu-kvm). The host is ubuntu 14.04 with the linux- - generic-lts-vivid kernel. + virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with + the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Triaged Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: New Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace
I don't quite get the point underlying Serge's preceding comment, so I'll describe the problem I'm experiencing with lxc and see whether Serge classifies it as a bug. On an ubuntu-vivid (amd64) host, create an unprivileged vivid container named 'vivid', lxc-create -n vivid -t download -- -d ubuntu -r vivid -a amd64 Start and attach to the container and create foo/bar.txt . Stop the container. Then form a second container named vivid_overlay, lxc-clone -s -B overlayfs vivid vivid_overlay Start and attach to vivid_overlay. Delete bar.txt (this should succeed). Attempt to delete foo. I get "Operation not permitted", even as root in the container. The same issue arises if I replace the overlay container with an ephemeral container, lxc-start-ephemeral -o vivid -n vivid_ephemeral -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1480411 Title: rm -r * fails to delete directories when using overlayfs in a user- namespace Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Invalid Bug description: rm -r * fails to delete directories when using overlayfs in a user- namespace. If overlayfs is mounted as follows, mount -n -t overlay overlay -o lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt and if lowerdir contains lowerdir/foo/bar.txt, then, rm -r mntpt/foo fails with error message, "rm: cannot remove ‘mntpt/foo’: Operation not permitted" strace shows, unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM (Operation not permitted) OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid kernel (3.19). The bug does not occur on ubuntu 14.04.2 with the default linux- generic 3.13 kernel. The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch, "overlayfs: allow unprivileged mounts" is added. (The patch is at, http://kernel.ubuntu.com/git/ubuntu/ubuntu- vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea) The bug occurs regardless of whether the filesystem underlying overlayfs is tmpfs or ext4. The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a virtual machine (qemu-system-x86_64). The host is ubuntu 14.04.2 with the default 3.13 kernel. A script which reproduces the bug is attached and is also available at http://paste.ubuntu.com/11974137/ Hardware: intel core2 duo processor in a macbook-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1480411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490267] Re: Regression in overlayfs
Some related information: A thread on the lxc mailing-list: https://lists.linuxcontainers.org/pipermail/lxc-users/2015-August/009854.html A related bug filed against lxc: https://bugs.launchpad.net/lxc/+bug/1486073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490267 Title: Regression in overlayfs Status in linux package in Ubuntu: Confirmed Bug description: When installing the linux-lts-vivid kernel in Ubuntu 14.04, there is a regression with overlayfs and unprivileged containers: 'failed to whiteout' Below the system information: - Kernel error: http://pastebin.com/iajXHbHZ - Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux - Executed LXC command: lxc-clone -s -B overlayfs orig test (both unprivileged containers) - LXC version: 1.0.7 We discussed this on the LXC user mailing list, and this is likely a bug in one of the patches that add support for unprivileged use of overlayfs. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 30 13:56 seq crw-rw 1 root audio 116, 33 Aug 30 13:56 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 Ec2AMI: ami-fceee9e1 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-central-1b Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb 1 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=dde0e30e-be54-43dc-9a44-5769353c2e27 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory StagingDrivers: visorutil Tags: trusty ec2-images staging Uname: Linux 3.19.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829340] Re: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0
apport-collect is not available in the BusyBox env. So, I cannot complete the command apport-collect 1829340 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829340 Title: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0 Status in linux package in Ubuntu: Incomplete Bug description: Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 0) PCIID: 8086:10fb subsystem 103c:17d0 I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported kernel from 18.04 v4.15. PXE boot process works well till the moment when the installer tries to load the ixgbe driver for NIC. The driver fails to initialize NIC with the following error messages in the syslog: ixgbe: Intel(r) 10 Gigabit PCI Express Network Driver - version 5.1.0-k ixgne: Copyright (c) 1999-20016 Intel Corporation ixgbe: probe of :03:00.0 failed with error -5 ixgbe: probe of :03:00.1 failed with error -5 I have used the most recent initrd and kernel from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/hwe-netboot/ubuntu-installer/amd64/ file linux initrd.gz linux: Linux/x86 Kernel, Setup Version 0x20d, bzImage, Version 4.15.0, Version 4.15.0-45, RO-rootFS, swap_dev 0x7, Normal VGA initrd.gz: gzip compressed data, was "initrd", from Unix, last modified: Wed Feb 20 06:36:36 2019, max compression Also I'd like to say that * the same issue with ixgbe 4.2.1-k if I use the installer of Ubuntu 16.04 with kernel v4.4 * ixgbe v4.2.1-k from SLES12SP2 works correctly. #this is SLES12 host with more info about ixgbe from SLES12. :~ # modinfo ixgbe filename: /lib/modules/4.4.90-92.50-default/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.2.1-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: F8D1434936208D466C73062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829340] Re: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0
The workaround has been found. Such network cards in DL20 Gen9 servers can work without changes in the driver if tune BIOS setting - disable SR-IOV in BIOS for the 10GB Intel Ethernet network card -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829340 Title: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0 Status in linux package in Ubuntu: Incomplete Bug description: Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 0) PCIID: 8086:10fb subsystem 103c:17d0 I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported kernel from 18.04 v4.15. PXE boot process works well till the moment when the installer tries to load the ixgbe driver for NIC. The driver fails to initialize NIC with the following error messages in the syslog: ixgbe: Intel(r) 10 Gigabit PCI Express Network Driver - version 5.1.0-k ixgne: Copyright (c) 1999-20016 Intel Corporation ixgbe: probe of :03:00.0 failed with error -5 ixgbe: probe of :03:00.1 failed with error -5 I have used the most recent initrd and kernel from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/hwe-netboot/ubuntu-installer/amd64/ file linux initrd.gz linux: Linux/x86 Kernel, Setup Version 0x20d, bzImage, Version 4.15.0, Version 4.15.0-45, RO-rootFS, swap_dev 0x7, Normal VGA initrd.gz: gzip compressed data, was "initrd", from Unix, last modified: Wed Feb 20 06:36:36 2019, max compression Also I'd like to say that * the same issue with ixgbe 4.2.1-k if I use the installer of Ubuntu 16.04 with kernel v4.4 * ixgbe v4.2.1-k from SLES12SP2 works correctly. #this is SLES12 host with more info about ixgbe from SLES12. :~ # modinfo ixgbe filename: /lib/modules/4.4.90-92.50-default/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.2.1-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: F8D1434936208D466C73062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829340] Re: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0
just to be more specific - we try Ubuntu 16.04.5 and kernel 4.15.0-33 and succeeded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829340 Title: ixgbe driver fails while loading in kernel for NIC 8086 :10fb (rev 01) subsystem 103c:17d0 Status in linux package in Ubuntu: Incomplete Bug description: Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 0) PCIID: 8086:10fb subsystem 103c:17d0 I have tried to install Ubuntu 16.04 with default kernel v4.4 and backported kernel from 18.04 v4.15. PXE boot process works well till the moment when the installer tries to load the ixgbe driver for NIC. The driver fails to initialize NIC with the following error messages in the syslog: ixgbe: Intel(r) 10 Gigabit PCI Express Network Driver - version 5.1.0-k ixgne: Copyright (c) 1999-20016 Intel Corporation ixgbe: probe of :03:00.0 failed with error -5 ixgbe: probe of :03:00.1 failed with error -5 I have used the most recent initrd and kernel from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer-amd64/current/images/hwe-netboot/ubuntu-installer/amd64/ file linux initrd.gz linux: Linux/x86 Kernel, Setup Version 0x20d, bzImage, Version 4.15.0, Version 4.15.0-45, RO-rootFS, swap_dev 0x7, Normal VGA initrd.gz: gzip compressed data, was "initrd", from Unix, last modified: Wed Feb 20 06:36:36 2019, max compression Also I'd like to say that * the same issue with ixgbe 4.2.1-k if I use the installer of Ubuntu 16.04 with kernel v4.4 * ixgbe v4.2.1-k from SLES12SP2 works correctly. #this is SLES12 host with more info about ixgbe from SLES12. :~ # modinfo ixgbe filename: /lib/modules/4.4.90-92.50-default/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.2.1-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: F8D1434936208D466C73062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872122] Re: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04
Currently, unable to use the Bluetooth device at all. In the UI, the scanning stuck with a spinning loader. The journal reports the same error reported by the author. ``` lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal ``` ``` uname -a Linux n552vw 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
The fix does not work for me: uname -r 5.4.0-33-generic ournalctl -b0 -u rtkit-daemon -- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05 EEST. -- Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy Service... Jun 04 18:26:06 n552vw systemd[1]: Started RealtimeKit Scheduling Policy Service. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully called chroot. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully dropped privileges. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully limited resources. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Canary thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Watchdog thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:49 n552vw
[Kernel-packages] [Bug 1760377] Re: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic
*** This bug is a duplicate of bug 1759920 *** https://bugs.launchpad.net/bugs/1759920 Confirmed, upgraded yesterday to 0-37 and Xorg started to hang on gdm3 boot. Tried lightdm but it hangs too. 0-36 works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760377 Title: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: I updated kernel to 4.13.0-37-generic, and after reboot, it freezes on the kde login screen. Even sysrq keys does not work. I rebooted again, and be able to enter password, then it freezes again on plasma loading screen. I finally selected 4.13.0-36-generic kernel from grub, and my computer booted normally. I guess there was a kernel panic, but it didn't show on screen, nor in system logs, or I cannot find it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 1 11:14:39 2018 DistUpgraded: 2017-10-02 23:05:26,340 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: kubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc 2nd Generation Core Processor Family Integrated Graphics Controller [152d:0875] NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc GF106M [GeForce GT 555M] [152d:0875] InstallationDate: Installed on 2012-12-20 (1927 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hasee QTH6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=5e2d0528-b52e-4165-9c44-c18ef0338b43 ro quiet splash video=VGA-2:d SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-02 (180 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: SU272 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HM65 dmi.board.vendor: Hasee dmi.board.version: TBD dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hasee dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrSU272:bd12/16/2011:svnHasee:pnQTH6:pvr03:rvnHasee:rnHM65:rvrTBD:cvnHasee:ct10:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: QTH6 dmi.product.version: 03 dmi.sys.vendor: Hasee version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Apr 1 11:07:30 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813672] Re: 4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked
Some kind of similar issue on ThinkPad X250 20CM004EMN. Switching back to 4.15.0-43-generic solved the problem. Booting with 4.15.0-44-generic on Ultra Dock station gives blank screen on login/display manager. Undocking does not solve the issue so only SysRq+REISUB or hard reboot help. X250 rejects to fall sleep on closed lid or Fn+4 combination. Tried on two different Ultra Dock stations with various monitors, the result is the same. Booting with 4.15.0-44-generic undocked brings login/display manager as expected. It is possible to dock after that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813672 Title: 4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked Status in linux package in Ubuntu: Confirmed Bug description: To reproduce, lock the screen while the laptop is docked. Box will go into some hung state where the only solution is to hard poweroff. Doesn't happen while undocked. Reverting to 4.15.0-43 kernel fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1218 F pulseaudio rochon 2115 F pulseaudio Date: Mon Jan 28 14:15:24 2019 InstallationDate: Installed on 2017-05-25 (613 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20HGS0CB00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=d26c36c8-1296-4878-a755-84517190e94c ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-08 (265 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HGS0CB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HGS0CB00:pvrThinkPadT470s:rvnLENOVO:rn20HGS0CB00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HGS0CB00 dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Same freezing error. Clean 18.10 Ubuntu instal. Processor: Ryzen Nvidia drivers installed from nvidia homepage. More frequently freezing when working with video inside kdenlive. But had freezes also when only chrome was playing music. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781049] Re: WiFi hard blocked after resuming laptop from suspend
Have exactly the same issue with Acer ex2519 n15w4 with Qualcomm Atheros QCA9565 wi-fi card in it. Wi-fi worked during system installation (with secure boot disabled as the original reporter mentioned). Not sure if computer was suspended or powered off, but once I booted it and wi-fi just stopped working and rfkill reported that device phy0 is hard blocked. The computer runs kernel 4.18.0-13-generic. I am happy to provide any additional information to solve the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781049 Title: WiFi hard blocked after resuming laptop from suspend Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythreya 1281 F pulseaudio /dev/snd/controlC1: mythreya 1281 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-26 (16 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion Notebook NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.87 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8096 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-30T14:39:45.608645 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2018-06-28T16:23:51.596655 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR71 1a9d81bf-e7f5-4f8a-956f-96180dc493e1 wifi 1531450229 Thu 12 Jul 2018 09:50:29 PM CDT yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlo1activated /org/freedesktop/NetworkManager/ActiveConnection/2 --
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I just want to add that I have the same problem on my Asus N552VW. I have managed to make it work from day 1, so hopefully this can help someone until the proper bug fix is provided. I have a laptop and an external monitor plugged via HDMI, everything is turned off. Simply turn on the laptop and load the OS, input your login/pass and get into system. Now close the laptop lid, then turn of the monitor. This are the only steps I can make an external monitor work with 20.04, kernel 5.4. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType:
[Kernel-packages] [Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
4.4-rc1 works just fine, so now I'm bisecting from 4.3 to 4.4-rc1, but it's also few thousand commits, something about 13 rounds to find. I'm on 14.04 LTS and bug appeared only in 3.16 and 3.19 kernels, all installations with 3.13 works OK. 3.16.45 - ok 3.16.46 and higher - error 3.19.25 - ok 3.19.26 and higher - error Bug was added at the end of July, but there were few hundreds of commits starting from 28 July and none of them directly linked to pata_amd or pata_acpi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536397 Title: [nForce2] pata_amd pata_acpi can't load Status in linux package in Ubuntu: Incomplete Bug description: The system is 15.04. Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I can boot the system only with 3.19.0-15-generic. I always update the system and check new kernel packages, but they have the same error. In dmesg I found: pata_amd :00:09.0: can't enable device: BAR 0 [io 0x01f0-0x01f7] not claimed pata_amd: probe of :00:09.0 failed with error -22 And analogical for pata_acpi. P.S. I have a suspicion to the option CONFIG_PCI_BUS_ADDR_T_64BIT=y . But I'm not linux kernel guru. --- ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paly 2672 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d4137d34-9c31-41b2-9557-b14531398f02 InstallationDate: Installed on 2015-11-14 (67 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/sda2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143.7 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev' Uname: Linux 3.19.0-15-generic i686 UpgradeStatus: Upgraded to vivid on 2015-12-05 (47 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: nVidia-nForce dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
And the winner is 4d6b4e69a245e9df4b84dba387596086cb66887d is the first bad commit commit 4d6b4e69a245e9df4b84dba387596086cb66887d Author: Jiang Liu Date: Wed Oct 14 14:29:41 2015 +0800 x86/PCI/ACPI: Use common interface to support PCI host bridge Use common interface to simplify ACPI PCI host bridge implementation. Signed-off-by: Jiang Liu Reviewed-by: Hanjun Guo Acked-by: Bjorn Helgaas Signed-off-by: Rafael J. Wysocki Actually it is good, not bad commit :) So, what's next? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536397 Title: [nForce2] pata_amd pata_acpi can't load Status in linux package in Ubuntu: Incomplete Bug description: The system is 15.04. Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I can boot the system only with 3.19.0-15-generic. I always update the system and check new kernel packages, but they have the same error. In dmesg I found: pata_amd :00:09.0: can't enable device: BAR 0 [io 0x01f0-0x01f7] not claimed pata_amd: probe of :00:09.0 failed with error -22 And analogical for pata_acpi. P.S. I have a suspicion to the option CONFIG_PCI_BUS_ADDR_T_64BIT=y . But I'm not linux kernel guru. --- ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paly 2672 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d4137d34-9c31-41b2-9557-b14531398f02 InstallationDate: Installed on 2015-11-14 (67 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/sda2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143.7 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev' Uname: Linux 3.19.0-15-generic i686 UpgradeStatus: Upgraded to vivid on 2015-12-05 (47 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: nVidia-nForce dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
It was impossible to resist temptation to find where the story began. It
all started between 4.1 and 4.2-rc1. Bisecting points to this commit:
3d9fecf6bfb8b12bc2f9a4c7109895a2a2bb9436 is the first bad commit
commit 3d9fecf6bfb8b12bc2f9a4c7109895a2a2bb9436
Author: Bjorn Helgaas
Date: Tue Jun 9 17:31:38 2015 -0500
x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing
We enable _CRS on all systems from 2008 and later. On older systems, we
ignore _CRS and assume the whole physical address space (excluding RAM and
other devices) is available for PCI devices, but on systems that support
physical address spaces larger than 4GB, it's doubtful that the area above
4GB is really available for PCI.
After d56dbf5bab8c ("PCI: Allocate 64-bit BARs above 4G when possible"), we
try to use that space above 4GB *first*, so we're more likely to put a
device there.
On Juan's Toshiba Satellite Pro U200, BIOS left the graphics, sound, 1394,
and card reader devices unassigned (but only after Windows had been
booted). Only the sound device had a 64-bit BAR, so it was the only device
placed above 4GB, and hence the only device that didn't work.
Keep _CRS enabled even on pre-2008 systems if they support physical address
space larger than 4GB.
Fixes: d56dbf5bab8c ("PCI: Allocate 64-bit BARs above 4G when possible")
Reported-and-tested-by: Juan Dayer
Reported-and-tested-by: Alan Horsfield
Link: https://bugzilla.kernel.org/show_bug.cgi?id=99221
Link: https://bugzilla.opensuse.org/show_bug.cgi?id=907092
Signed-off-by: Bjorn Helgaas
CC: sta...@vger.kernel.org # v3.14+
** Bug watch added: Linux Kernel Bug Tracker #99221
http://bugzilla.kernel.org/show_bug.cgi?id=99221
** Bug watch added: bugzilla.opensuse.org/ #907092
http://bugzilla.opensuse.org/show_bug.cgi?id=907092
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1536397
Title:
[nForce2] pata_amd pata_acpi can't load
Status in linux package in Ubuntu:
Triaged
Bug description:
The system is 15.04.
Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I
can boot the system only with 3.19.0-15-generic.
I always update the system and check new kernel packages, but they
have the same error.
In dmesg I found:
pata_amd :00:09.0: can't enable device: BAR 0 [io 0x01f0-0x01f7] not
claimed
pata_amd: probe of :00:09.0 failed with error -22
And analogical for pata_acpi.
P.S. I have a suspicion to the option CONFIG_PCI_BUS_ADDR_T_64BIT=y . But I'm
not linux kernel guru.
---
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paly 2672 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=d4137d34-9c31-41b2-9557-b14531398f02
InstallationDate: Installed on 2015-11-14 (67 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic
root=/dev/sda2 ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
Tags: vivid
UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev'
Uname: Linux 3.19.0-15-generic i686
UpgradeStatus: Upgraded to vivid on 2015-12-05 (47 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/07/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: nVidia-nForce
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load
Actually, this leads to a workaround. Adding kernel option "pci=nocrs" in grub allows to boot currents kernels. I'm not sure whether it leads to some other problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1536397 Title: [nForce2] pata_amd pata_acpi can't load Status in linux package in Ubuntu: Triaged Bug description: The system is 15.04. Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I can boot the system only with 3.19.0-15-generic. I always update the system and check new kernel packages, but they have the same error. In dmesg I found: pata_amd :00:09.0: can't enable device: BAR 0 [io 0x01f0-0x01f7] not claimed pata_amd: probe of :00:09.0 failed with error -22 And analogical for pata_acpi. P.S. I have a suspicion to the option CONFIG_PCI_BUS_ADDR_T_64BIT=y . But I'm not linux kernel guru. --- ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paly 2672 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=d4137d34-9c31-41b2-9557-b14531398f02 InstallationDate: Installed on 2015-11-14 (67 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic root=/dev/sda2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143.7 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev' Uname: Linux 3.19.0-15-generic i686 UpgradeStatus: Upgraded to vivid on 2015-12-05 (47 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: nVidia-nForce dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1379524] Re: Weak wifi signal and bluetooth missing firmware
I have exactly the same issue on my HP Pavilion 15-p163nr. Issue: weak signal, frequent disconnects. Kubuntu 14.04 LTS Uname both: Linux 3.13.0-37-generic x86_64 and Uname: Linux 3.13.0-39-generic x86_64 And I did the same thing before I found this thread — build the driver from source found at http://www.broadcom.com/support/802.11/linux_sta.php and install it. After that the signal is much better — but still after some time it loses the connectivity (without any apparent indication — i.e. 3 bars in notification icon but websites load forever. In my attempt to fix that I did the following: 1. Set IPv6 in my connection settings to Ignore 2. Enforce the regulatory domain to my country code (from dmesg it seemed that regulatory domain was periodically switching from 'world' to 'Ru'): sudo sed -i 's/^REG.*=$/&RU/' /etc/default/crda sudo iw reg set RU 3. (Just in case): sudo update-initramfs -u And it seems to work almost fine now. I also tried 14.10 and had issues with wifi too — the signal was OK but it constantly disconnected and even to the point where my aweful DLink Dir-300 had to be restarted — connection was repeatedly lost on my other devices too. PS. Hendrik, as far as I understand the 5 Ghz frequency is not supported by the controller itself (at least for Pavilion 15-p163nr). __ $ lspci -vnn -d 14e4: 08:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:2230] Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at b550 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: wl __ $ lsmod | grep "brcmsmac\|ssb\|wl\|b43\|bcma" wl 6363686 0 cfg80211 484040 1 wl __ That's what I'm having now in: $ dmesg | grep wl [ 11.946547] wl: module license 'unspecified' taints kernel. [ 11.949084] wl: module verification failed: signature and/or required key missing - tainting kernel [ 8974.077536] Modules linked in: pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) bnep rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_core bluetooth videodev hp_wmi sparse_keymap snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel snd_hda_codec snd_hwdep joydev snd_pcm serio_raw snd_page_alloc snd_seq_midi snd_seq_midi_event lpc_ich snd_rawmidi wl(POX) snd_seq snd_seq_device rtsx_pci_ms cfg80211 snd_timer snd memstick mei_me mei soundcore hp_accel lis3lv02d hp_wireless input_polldev intel_smartconnect mac_hid parport_pc ppdev lp parport rtsx_pci_sdmmc nouveau i915 psmouse mxm_wmi ttm ahci i2c_algo_bit libahci drm_kms_helper r8169 drm mii rtsx_pci wmi video [ 8974.077637] CPU: 0 PID: 441 Comm: wl_event_handle Tainted: P OX 3.13.0-39-generic #66-Ubuntu [ 8974.077847] [] wl_notify_roaming_status+0xcb/0x150 [wl] [ 8974.077942] [] wl_event_handler+0x62/0x220 [wl] [ 8974.078014] [] ? wl_cfg80211_resume+0x440/0x440 [wl] Let me know if any details from me could help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1379524 Title: Weak wifi signal and bluetooth missing firmware Status in “bcmwl” package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 14.04 on my new HP Pavilion 15-020ng with Broadcom BCM43142 hybrid wifi/bluetooth chipset the official driver from Broadcom does not work correctly. On 2.4 GHz the wifi signal is so low that the connection is interrupted on a regular basis (network manager shows 26 Mb/s), other devices (notebook, tablet) do have a normal signal at the same position and even this laptop has a good signal with Windows 7 (Dual-Boot). In addition, Bluetooth does not work because the driver reports missing firmware but there does not seem to be official firmware available anywhere. The exact device name: 08:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) The 5 Ghz frequency seems to be not supported by the driver according to the README file and does not work at all. My router is set to use WPA2-PSK with AES, which is the only possible option besides WPA or WPA/WPA2-mixed. I am using the official wl driver that was installed by default, also tried reinstalling via "sudo apt-get install bcmwl-kernel-source --reinstall" without improvement and "sudo iwconfig wlan0 power off". Also blacklisted b43, brcmsmac and bcma as suggested by "Linux Wireless". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0
