[Kernel-packages] [Bug 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
This bug was fixed in the package linux - 4.2.0-35.40 --- linux (4.2.0-35.40) wily; urgency=low [ Brad Figg ] * Release Tracking Bug - LP: #1557706 [ Upstream Kernel Changes ] * Revert "workqueue: make sure delayed work run in local cpu" - LP: #1556269 * Revert "ALSA: hda - Fix noise on Gigabyte Z170X mobo" - LP: #1556269 * KVM: VMX: Fix host initiated access to guest MSR_TSC_AUX - LP: #1552592 * locking/qspinlock: Move __ARCH_SPIN_LOCK_UNLOCKED to qspinlock_types.h - LP: #1545330 * [media] usbvision fix overflow of interfaces array - LP: #1556269 * [media] usbvision: fix crash on detecting device with invalid configuration - LP: #1556269 * ASN.1: Fix non-match detection failure on data overrun - LP: #1556269 * iw_cxgb3: Fix incorrectly returning error on success - LP: #1556269 * EVM: Use crypto_memneq() for digest comparisons - LP: #1556269 * vmstat: explicitly schedule per-cpu work on the CPU we need it to run on - LP: #1556269 * x86/entry/compat: Add missing CLAC to entry_INT80_32 - LP: #1556269 * iio-light: Use a signed return type for ltr501_match_samp_freq() - LP: #1556269 * iio: add IIO_TRIGGER dependency to STK8BA50 - LP: #1556269 * iio: add HAS_IOMEM dependency to VF610_ADC - LP: #1556269 * iio: dac: mcp4725: set iio name property in sysfs - LP: #1556269 * iommu/vt-d: Fix 64-bit accesses to 32-bit DMAR_GSTS_REG - LP: #1556269 * iio: light: acpi-als: Report data as processed - LP: #1556269 * iio:adc:ti_am335x_adc Fix buffered mode by identifying as software buffer. - LP: #1556269 * ASoC: rt5645: fix the shift bit of IN1 boost - LP: #1556269 * ARCv2: STAR 9000950267: Handle return from intr to Delay Slot #2 - LP: #1556269 * cgroup: make sure a parent css isn't offlined before its children - LP: #1556269 * ARM: OMAP2+: Fix wait_dll_lock_timed for rodata - LP: #1556269 * ARM: OMAP2+: Fix l2dis_3630 for rodata - LP: #1556269 * ARM: OMAP2+: Fix save_secure_ram_context for rodata - LP: #1556269 * ARM: OMAP2+: Fix l2_inv_api_params for rodata - LP: #1556269 * ARM: OMAP2+: Fix ppa_zero_params and ppa_por_params for rodata - LP: #1556269 * rtlwifi: rtl8821ae: Fix 5G failure when EEPROM is incorrectly encoded - LP: #1556269 * PCI/AER: Flush workqueue on device remove to avoid use-after-free - LP: #1556269 * ARM: dts: Fix wl12xx missing clocks that cause hangs - LP: #1556269 * libata: disable forced PORTS_IMPL for >= AHCI 1.3 - LP: #1556269 * mac80211: Requeue work after scan complete for all VIF types. - LP: #1556269 * rfkill: fix rfkill_fop_read wait_event usage - LP: #1556269 * ARM: dts: at91: sama5d4: fix instance id of DBGU - LP: #1556269 * ARM: dts: at91: sama5d4ek: add phy address and IRQ for macb0 - LP: #1556269 * ARM: dts: at91: sama5d4 xplained: fix phy0 IRQ type - LP: #1556269 * crypto: shash - Fix has_key setting - LP: #1556269 * Input: vmmouse - fix absolute device registration - LP: #1556269 * spi: atmel: fix gpio chip-select in case of non-DT platform - LP: #1556269 * drm/i915/dp: fall back to 18 bpp when sink capability is unknown - LP: #1556269 * ALSA: usb-audio: Fix OPPO HA-1 vendor ID - LP: #1556269 * ALSA: usb-audio: Add native DSD support for PS Audio NuWave DAC - LP: #1556269 * ALSA: usb-audio: Add quirk for Microsoft LifeCam HD-6000 - LP: #1556269 * target: Fix WRITE_SAME/DISCARD conversion to linux 512b sectors - LP: #1556269 * crypto: algif_hash - wait for crypto_ahash_init() to complete - LP: #1556269 * iio: inkern: fix a NULL dereference on error - LP: #1556269 * iio: pressure: mpl115: fix temperature offset sign - LP: #1556269 * intel_scu_ipcutil: underflow in scu_reg_access() - LP: #1556269 * ALSA: seq: Fix race at closing in virmidi driver - LP: #1556269 * ALSA: rawmidi: Remove kernel WARNING for NULL user-space buffer check - LP: #1556269 * ALSA: pcm: Fix potential deadlock in OSS emulation - LP: #1556269 * ALSA: seq: Fix yet another races among ALSA timer accesses - LP: #1556269 * ALSA: timer: Code cleanup - LP: #1556269 * ALSA: timer: Fix link corruption due to double start or stop - LP: #1556269 * libata: fix sff host state machine locking while polling - LP: #1556269 * MIPS: Fix buffer overflow in syscall_get_arguments() - LP: #1556269 * cputime: Prevent 32bit overflow in time[val|spec]_to_cputime() - LP: #1556269 * drm: add helper to check for wc memory support - LP: #1556269 * drm/radeon: mask out WC from BO on unsupported arches - LP: #1556269 * drm/amdgpu: mask out WC from BO on unsupported arches - LP: #1556269 * ASoC: dpcm: fix the BE state on hw_free - LP: #1556269 * drm/amdgpu: move gmc7 support out of CIK dependency - LP: #1556269 * drm/amdgpu: iceland use CI based M
[Kernel-packages] [Bug 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Verified that the test case from comment #3 passes with 4.2.0-35.40. ** Tags removed: verification-needed-wily ** Tags added: verification-done-wily -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-wily -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
This bug was fixed in the package linux - 4.4.0-14.30 --- linux (4.4.0-14.30) xenial; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1557508 * Current 4.4 kernel won't boot on powerpc (LP: #1557130) - powerpc: Fix dedotify for binutils >= 2.26 * ZFS: send fails to transmit some holes [corruption] (LP: #1557151) - Illumos 6370 - ZFS send fails to transmit some holes * Request to cherry-pick uvcvideo patch for Xenial kernel support of RealSense camera (LP: #1557138) - UVC: Add support for ds4 depth camera * use after free of task_struct->numa_faults in task_numa_find_cpu (LP: #1527643) - sched/numa: Fix use-after-free bug in the task_numa_compare * overlay fs regression: chmod fails with "Operation not permitted" on chowned files (LP: #1555997) - ovl: copy new uid/gid into overlayfs runtime inode * Miscellaneous Ubuntu changes - SAUCE: Dump stack when X.509 certificates cannot be loaded -- Tim Gardner Mon, 14 Mar 2016 07:16:19 -0600 ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-package
[Kernel-packages] [Bug 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-wily -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Committed -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: In Progress Status in linux source package in Xenial: Fix Committed Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Nice work Seth, 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Actually there's already a fix for this in Linus' tree which tests fine for me. -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Reverting that patch fixes the regression. I'll send the patch to revert and report the bug upstream. -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
In the steps from comment #3, after the chown ls shows the file in both the upperdir and the mount as owned by $USER:$USER. However the inode from the overlayfs superblock which ovl_setattr() passes to inode_change_ok() seems to still be owned by root. This seems to be because ovl_getattr() gets the attributes from the inode in the upper/lower fs and not from the overlayfs inode. Actually, I don't think the attributes were ever being copied to the overlayfs inode. "ovl: setattr: check permissions before copy-up" adds a call to inode_change_ok() on the overlayfs inode at the beginning of ovl_setattr(). Before that it only ever checked that the change was okay for the inode in upperdir, so the fact that the attributes weren't copied over didn't cause a failure. That's a commit we got from upstream stable, and sure enough the bug exists in 4.5-rc7 as well. ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Overlayfs commits between -8 and -10: 84005e9 UBUNTU: SAUCE: overlayfs: Propogate nosuid from lower and upper mounts 6b833b0 UBUNTU: SAUCE: overlayfs: Be more careful about copying up sxid files 9de69709 UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs 21b8f14 UBUNTU: SAUCE: overlayfs: Use mounter's credentials instead of selectively raising caps 0c29f9e UBUNTU: SAUCE: overlayfs: Enable user namespace mounts for the "overlay" fstype 98a3740 UBUNTU: SAUCE: overlayfs: when copying up and reading directories ensure mounter had permissions V2 204bb1c UBUNTU: SAUCE: overlay: add backwards compatible overlayfs format support V4 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: performing-bisect ** Also affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Triaged -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Commits from upstream between -8 and -10: 8373f65 ovl: setattr: check permissions before copy-up 7193e80 ovl: root: copy attr 367e439 ovl: check dentry positiveness in ovl_cleanup_whiteouts() fa93219 ovl: use a minimal buffer in ovl_copy_xattr 85a7ed3 ovl: allow zero size xattr -- 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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 1555997] Re: overlay fs regression: chmod fails with "Operation not permitted" on chowned files
Reproducer is available, not hw specific, so doesn’t need additional logs. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1555997 Title: overlay fs regression: chmod fails with "Operation not permitted" on chowned files Status in linux package in Ubuntu: Confirmed Bug description: This is a regression in Xenial's kernel 4.4.0-9 or 4.4.0-10. See comment #3 for simple reproducer. ORIGINAL BUG REPORT === I'm investigating some failures in autopkgtest's testsuite, and stumbled over something really weird: In an ephemeral container it is apparently not possible any more to chmod files that started out being root owned and got chowned later: $ sudo lxc-start-ephemeral -o adt-wily (log in as ubuntu/ubuntu) ubuntu@adt-wily-hvzj1eoa:~$ echo hello | sudo tee /tmp/testfile [sudo] password for ubuntu: hello ubuntu@adt-wily-hvzj1eoa:~$ sudo chown ubuntu:ubuntu /tmp/testfile ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile chmod: changing permissions of ‘/tmp/testfile’: Operation not permitted However, if the file was *not* previously chowned, it works as expected: ubuntu@adt-wily-hvzj1eoa:~$ echo hello > /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod +x /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ chmod -x /tmp/testfile2 (no errors and testfile2 becomes executable) There is no visible permission difference in the files at all, other than being group-writable (but changing the group w bit in either direction does not change the error at all): -rw-r--r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile -rw-rw-r-- 1 ubuntu ubuntu 6 Mar 11 10:26 /tmp/testfile2 ubuntu@adt-wily-hvzj1eoa:~$ stat /tmp/testfile* File: ‘/tmp/testfile’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 28 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:19.574364117 +0100 Modify: 2016-03-11 10:26:19.574364117 +0100 Change: 2016-03-11 10:26:21.930343210 +0100 Birth: - File: ‘/tmp/testfile2’ Size: 6 Blocks: 8 IO Block: 4096 regular file Device: 15h/21d Inode: 29 Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/ ubuntu) Gid: ( 1000/ ubuntu) Access: 2016-03-11 10:26:58.730145919 +0100 Modify: 2016-03-11 10:26:58.730145919 +0100 Change: 2016-03-11 10:27:44.530203985 +0100 Birth: - There are also no ACLs involved (I checked with getfacl). This does not happen with a normal lxc-start, so this might very well be a bug in Linux' overlayfs. However, it also does not happen with the more modern "sudo lxc-copy -n adt-wily --ephemeral --foreground" -- bug perhaps this isn't using overlayfs? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0~rc9-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Mar 11 10:21:20 2016 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx dnsmasq.conf: enable-tftp tftp-root=/tmp/tftp dhcp-boot=pxelinux.0 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555997/+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
