[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
This is unbelieveable: - Ubuntu Xenial is shipping new broken kernels with a known REGRESSION ! - For more than two weeks a fix is known and "InProgress" (whatever this means). That does however not prevent new broken kernels from being released (4.4.0-42 and 4.4.0-43). - Moreover all of these broken kernels have never gone through -proposed. Isn't this what -proposed is supposed to be for?!? - For about a day a fixed and approved kernel (4.4.0-44) has finally made it to -proposed. But this again does not prevent another broken kernel (4.4.0-45) to be released directly, without going through -proposed. - And to top it all, the git repo does not seem to be up to date. git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git I am really pissed! Robert -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name:
[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
The -proposed kernel works for me and fixes the problem. Thanks! Robert -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
I really don't understand what's going on here. It's been another 6 days now. There has been another (broken) kernel update for xenial (4.4.0-43) which did not include this fix, and which also did not go through -proposed. Instead xenial-proposed is still at at 4.4.0-41, which is broken as well. Two "stable" kernel updates with a known regression and a simple fix. How is this possible? And how does this fit with xenial being an LTS-Release? This really ain't funny any more! For now I have build the packages with the fix applied for amd64 and I'll try to keep up with new broken kernels. In case anybody else needs them: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 89C9B5AE sudo apt-add-repository -u 'http://ubuntu.repo.uni-hannover.de/ubuntu xenial pub' Or get the key from here: http://ubuntu.repo.uni-hannover.de/ubuntu/luh-deb-repo.gpg.key Regards, Robert -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias:
[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
I am very disappointed that another broken "stable" kernel (4.4.0-42.62) was just released for xenial, even though this problem and the fix have been known for about a week! Why? What can I do to speed up the progress? I really need a working kernel on xenial! Or do I have to build it myself and roll it out to our systems? Thanks, Robert. -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
Just a note: 4.4.0-41.61 from xenial-proposed is still broken. -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
I can confirm that the 0001-autofs4-Use-real_cred-for-uid-gid-in- packets.patch fixes the problem. I have tried the kernel located here: http://people.canonical.com/~sforshee/lp1629204/ And I have also applied the patch an top of the 4.4.0-38 kernel (commit be687e48ba9778ab2f28513bd50e1b274ba31f68) this fixes the problem there as well. Please release a fixed kernel for xenial asap! Thanks to everyone involved. Regards Robert. -- 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/1629204 Title: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: SRU Justification Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds" causes a regression in the requester uid and gid passed to userspace during automount, as the current credentials during automount are those of root and not the user who requested the mount. Fix: Use current->real_cred instead of current->cred for getting the requester's uid and gid. Regression Potential: Minimal. current->cred and current->real_cred are the same except when credentials are overridden, thus current->real_cred contains the same credentials that autofs had been using prior to the change which overrides the credentials during automount. --- Hello, I have run into a bug relating autofs's parameter substitution (e.g. UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40. Kernel version 4.4.0-28 does things correctly but testing intermediate kernel versions is hard due to earlier bugs related with fs's. Incorrect parameter substitution makes CIFS mounting with variable credentials impossible. Wat was expected: $UID in autofs map are substituted by the uid of the user that starts the auto-mounting process. What actually happens: Root's uid (0) is substituted instead. This ill parameter substitution likely caused by recent fixes resolving permissions problems for nfs/cifs mounts and dfs referrals (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount with the filesystems creds' but that is a wild guess. Furthermore; playing with the force_standard_program_map_env settings in autofs.conf and prefixing variables with 'AUTOFS_' does not solve anything. Yours kindly, Chris Additional info lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: run1 3015 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214 InstallationDate: Installed on 2016-09-19 (10 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: enp0s8no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-40-generic N/A linux-backports-modules-4.4.0-40-generic N/A linux-firmware1.157.3 RfKill: Tags: xenial Uname: Linux 4.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
*** This bug is a duplicate of bug 1629204 *** https://bugs.launchpad.net/bugs/1629204 This bug seems like a duplicate of this one filed moments beforem mine: http://bugs.launchpad.net/bugs/1629204 The came to the same conclusion. -- 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+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 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
Tim - thanks for that advice!
Now I'm finally there:
git bisect good
ca6fe3344554d31ac9c0f7e2e6be490c2d5d501f is the first bad commit
commit ca6fe3344554d31ac9c0f7e2e6be490c2d5d501f
Author: Eric W. Biederman <ebied...@xmission.com>
Date: Tue Sep 6 09:32:01 2016 -0500
fs: Call d_automount with the filesystems creds
BugLink: http://bugs.launchpad.net/bugs/1612135
Seth Forshee reported a mount regression in nfs autmounts
with "fs: Add user namespace member to struct super_block".
It turns out that the assumption that current->cred is something
reasonable during mount while necessary to improve support of
unprivileged mounts is wrong in the automount path.
To fix the existing filesystems override current->cred with the
init_cred before calling d_automount and restore current->cred after
d_automount completes.
To support unprivileged mounts would require a more nuanced cred
selection, so fail on unprivileged mounts for the time being. As none
of the filesystems that currently set FS_USERNS_MOUNT implement
d_automount this check is only good for preventing future problems.
Fixes: 6e4eab577a0c ("fs: Add user namespace member to struct super_block")
Tested-by: Seth Forshee <seth.fors...@canonical.com>
Signed-off-by: "Eric W. Biederman" <ebied...@xmission.com>
(backported from commit aeaa4a79ff6a5ed912b7362f206cf8576fca538b)
Signed-off-by: Seth Forshee <seth.fors...@canonical.com>
Acked-by: Stefan Bader <stefan.ba...@canonical.com>
Acked-by: Colin King <colin.k...@canonical.com>
Acked-by: Brad Figg <brad.f...@canonical.com>
Signed-off-by: Tim Gardner <tim.gard...@canonical.com>
:04 04 3b16a342088c0cfead081f63bc7fe9bed93bcf00
2634a48c59a1c6b313be2d8406644fd9d0e18a60 M fs
** Attachment added: "Git bisect log showing leading to the first bad commit."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4756633/+files/git_bisect_log_final
--
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/1629205
Title:
regression: with linux-image-4.4.0-38-generic autofs tries to acess
folders as root instead of the user
Status in linux package in Ubuntu:
Confirmed
Bug description:
Running with linux-image-4.4.0-38-generic autofs is not working
properly anymore: when I try to access a autofs-monitored folder as
normal user "joe" the environment variable $AUTOFS_USER inside the
auto mounter map script is set to "root" instead of the user "joe".
A little background information: in our setup the autofs master map
/etc/auto.master contains a line:
/mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose
The script /etc/auto.cifs-shares contains for debugging purposes the
lines:
DEBUG=true
$DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':"
$DEBUG && logger -p debug -- "$(env|grep AUTOFS)"
and
if test "$1" = "$AUTOFS_USER" ; then
## First generate automount map
[..]
else
logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access
wrong directory '$1'"
fi
Which yields to the following errors in the logs:
Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3
AUTOFS_HOME=/root
AUTOFS_GID=0
AUTOFS_UID=0
AUTOFS_GROUP=root
AUTOFS_USER=root
Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User
'root' tried to access wrong directory 'joe'
Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe
failed
Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe
So for some reason autofs with this kernel gets the environment variables
wrong.
Running an older Kernel like linux-image-4.4.0-36-generic does not show this
problem and the cifs shares work as expected.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: euhus 1711 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Sep 30 09:36:31 2016
HibernationDevice: RESUME=U
[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
Thanks for the offer Joseph! I have read your answer a bit late, so I am already on my 9th kernel (all good so far). The docs were quite good and I have wanted to try out "that bisect thing" for quite a while :) (It's just a bit annoying that it takes about half an hour to compile on a i5-6500 with 16G RAM. I had expected a bit less.) But now I have run into the problem, that I cannot build the current bisect point. I have cloned the kernel repo via git clone git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git I have attached the git bisect log up to the current point. When the compile is just about to be finished it fails with: EE: 36 symbols changed hash and weren't ignored II: Module hash change summary... vmlinux : 36 II: Done debian/rules.d/4-checks.mk:3: die Regel für Ziel „abi-check-generic“ scheiterte make: *** [abi-check-generic] Fehler 1 Sorry it's in German, I can redo it in english. I will attach a longer trace. I have always compiled doing a clean first: fakeroot debian/rules clean && fakeroot debian/rules binary-headers binary-generic So how do I go on from here? ** Attachment added: "git bisect log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755113/+files/git_bisect_log -- 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release: 16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc.
[Kernel-packages] [Bug 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
** Attachment added: "The current git status" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755115/+files/git_status -- 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+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 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
** Attachment added: "longer trace of the build error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+attachment/4755114/+files/build-error.log -- 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+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 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
** Tags added: kernel-bug-exists-upstream ** 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Confirmed Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+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 1629205] Re: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
Hi Joseph, yes, the problem started directly after the recent upgrade to linux- image-4.4.0-38-generic. I have never encountered this bug before, I know for certain that 4.4.0-36 works fine (as I have said before). Versions 4.4.0-34 and 4.4.0-22 are also without a problem. The mainline kernel shows the same problem; I have tried: linux-image-4.8.0-040800-generic_4.8.0-040800.201610022031_amd64.deb v4.8 (c8d2bc9bc39ebea8437fd974fdbc21847bb897a3) To me it looks like this bug was introduced between 4.4.0-36 and 4.4.0-38. I will try bisecting these versions following the instructions in the Wiki. Regards, Robert -- 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: Incomplete Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629205/+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 1629205] [NEW] regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user
Public bug reported: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX root[7613]: AUTOFS_SHOST=pc203re3 AUTOFS_HOME=/root AUTOFS_GID=0 AUTOFS_UID=0 AUTOFS_GROUP=root AUTOFS_USER=root Sep 29 17:03:20 pcXX root[7614]: /etc/auto.cifs-shares: Error: User 'root' tried to access wrong directory 'joe' Sep 29 17:03:20 pcXX automount[7557]: lookup(program): lookup for joe failed Sep 29 17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe So for some reason autofs with this kernel gets the environment variables wrong. Running an older Kernel like linux-image-4.4.0-36-generic does not show this problem and the cifs shares work as expected. other Info: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 uname -r 4.4.0-38-generic If you need any further info or testing, please let me know. Thanks, Robert Euhus ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: euhus 1711 F pulseaudio CurrentDesktop: GNOME Date: Fri Sep 30 09:36:31 2016 HibernationDevice: RESUME=UUID=1aae5293-ed3d-4dae-a8b5-54d831262f4a IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: Dell Inc. OptiPlex 5040 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=adae86bf-dc79-4962-aa5f-41a1a037c8ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0R790T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd01/15/2016:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0R790T:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 5040 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1629205 Title: regression: with linux-image-4.4.0-38-generic autofs tries to acess folders as root instead of the user Status in linux package in Ubuntu: New Bug description: Running with linux-image-4.4.0-38-generic autofs is not working properly anymore: when I try to access a autofs-monitored folder as normal user "joe" the environment variable $AUTOFS_USER inside the auto mounter map script is set to "root" instead of the user "joe". A little background information: in our setup the autofs master map /etc/auto.master contains a line: /mnt/cifs /etc/auto.cifs-shares --timeout=300 --verbose The script /etc/auto.cifs-shares contains for debugging purposes the lines: DEBUG=true $DEBUG && logger -p debug -- "$0: running 'env|grep AUTOFS':" $DEBUG && logger -p debug -- "$(env|grep AUTOFS)" and if test "$1" = "$AUTOFS_USER" ; then ## First generate automount map [..] else logger -p debug -- "$0: Error: User '$AUTOFS_USER' tried to access wrong directory '$1'" fi Which yields to the following errors in the logs: Sep 29 17:03:20 pcXX ro
[Kernel-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
Jarno Suni, thanks for the reply. First I would like to stress, that I still don't think that running all the KERNELS postINSTALL hooks while REMOVING the -extra package is the right thing todo. The only thing I can see that is really needed is the recreation of the initrd on installation and revmoval of that package (please correct me if I'm wrong!). So I think this is the only thing that should be done. Even recreating the GRUB config is unnessecary and a waste of time. So working around this in the /etc/kernel/postinst.d/apt-auto-removal script is imho not the right way to do this. That being said, this seems like the only available option right now. I have taken a closer look at your "Fixed again" script and made some adjustments (comparing with apt 1.0.1ubuntu2.10 from 14.04): - The version you have uploaded does not run properly, because some backslash-escapes for line breaks are missing (leading to "broken pipe" error). - In the check if the kernel given in argument is desired to be removed the "exit" from the awk statement causes another broken pipe if the match is not the last kernel. It is not needed, so I removed it. - The awk regex for creating the "list" of installed kernel versions is wrong ( only ' ' instead of '[ ]+' ), so the list is always empty. I don't see the advantage of using DPKG_QUERY here compared to the original which just uses DPKG. So to keep changes minimal I have reverted it to the old version. - The shortened check if we have more than two kernels to keep already may lead to keeping one more kernel (3 in total) than in the original, which is fine by me. - Again to keep changes (diff) minimal I have reordered the versions for the "kernel" variable like they are in the original. - The use of dpkg-query looks somehow awkward to me (but maybe it's just me). I'll attach my updated version of the /etc/kernel/postinst.d/apt-auto- removal script I have just run a few tests and it seems to work better than the original for now. I'll do some more testing right now. Regards, Robert. ** Attachment added: "updated /etc/kernel/postinst.d/apt-auto-removal script" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4551868/+files/apt-auto-removal -- 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/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one Status in One Hundred Papercuts: Triaged Status in apt package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: After installing a 3rd kernel currently 3.19.0-12-generic, the /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the 3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to be autoremoved. But once autoremove is completed the machine requests to be rebooted and at that time the /etc/apt/apt.conf.d /01autoremove-kernels file lists the 3.19.0-12-generic and 3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is requested to be autoremoved leaving only one kernel the latest one 3.19.0-12-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 5 17:03:01 2015 InstallationDate: Installed on 2015-04-02 (3 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440608/+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 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
Hi all,
sorry, the apt-auto-removal script attached above contained some debug
echo statements. Which were harmless, but unnessecary.
Testing and thinking a bit more about the problem I have come to the
conclusion, that upon removal of a linux-image-extra package the only
right thing to do is not to touch the list of kernels not for auto-
remove (/etc/apt/apt.conf.d/01autoremove-kernels) at all. We should just
leave it the way it is.
Reasoning: consider the following example:
- We have linux-image{,-extra}-1, linux-image{,-extra}-2 and
linux-image{,-extra}-3 installed.
- We now remove linux-image-extra-2 ; now we have two possible cases:
- a) linux-image-2 is not going to be removed, so we should not remove it
from the list
- b) linux-image-2 is removed afterwards, in which case it would not matter,
if we had removed it from the list.
Either way we have no way of knowing what will happen to the linux-image-2
package, while we are removing the linux-image-extra-2 package. So the only
sensible thing is imho not touching the list in this case at all.
This is what the updated script in my attachment does now.
Moreover, looking at this case from another perspective, it looks like
it would be a good thing to recreate the list at the time of the removal
of the linux-image-2 package! At this point it would be nice to prevent
linux-image-3 AND linux-image-1 from being auto-removed later on.
but this would be another bug report, I guess.
Even even updating this list upon installation of an linux-image-extra
package is questionable, since again we have no way of knowing, what the
user had in mind. Of course, the linux-image needs to be installed
(since it is a dependency), but maybe we are just installing all the
-extra packages for all the installed kernels? It probably doesn't do
too much harm in this case, but it is not very useful either.
I think, that this shows again, that executing all of the kernel-post-
install hooks while acting on the rather unrelated -extra package is not
the best way. Since recreating the initrd is the only thing we need,
this is the only thing we should do on installation and removal of the
-extra package!
So I see the updated /etc/kernel/postinst.d/apt-auto-removal script in
the attachment not really as a solution to this problem, but more as a
workaround for the broken linux-image-extra package install- and remove-
hooks.
Regards,
Robert.
** Attachment added: "updated /etc/kernel/postinst.d/apt-auto-removal script to
exit on removal of image-extra package"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4551880/+files/apt-auto-removal
--
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/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
except the latest one
Status in One Hundred Papercuts:
Triaged
Status in apt package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
After installing a 3rd kernel currently 3.19.0-12-generic, the
/etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
to be autoremoved. But once autoremove is completed the machine
requests to be rebooted and at that time the /etc/apt/apt.conf.d
/01autoremove-kernels file lists the 3.19.0-12-generic and
3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
requested to be autoremoved leaving only one kernel the latest one
3.19.0-12-generic.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apt 1.0.9.7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 5 17:03:01 2015
InstallationDate: Installed on 2015-04-02 (3 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1440608/+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 1375310] Re: Removing linux-image-extra-X-generic deletes initramfs
@ Andy Whitcroft: - in the commit d7235802d7735e53936c5ccfbe9e071021b394fb you write regarding linux-image-extra: "As it also depends on linux-image we know that linux-image will have been installed before it, and will be removed after it." The last part is not correct. We have no way of knowing, if the linux-image will be removed as well. Please see https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/comments/37 for a more detailed reasoning. Since all we need on installation and removal of linux-image-extras is a rebuild of the corresponding version of the initrd, I would say this is all we should do. And not abuse and run all of the kernel post-install hooks on both occasions. At least on my systems I don't see any good reason to run any of the other hooks. Please see the attached patch for the postinst and postrm hooks for the -extra package. Regards, Robert. ** Patch added: "Updated postinst and postrm hooks for -extra package to only recreate the initrd" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375310/+attachment/4551893/+files/update-only-initrd-for-extra-package.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/1375310 Title: Removing linux-image-extra-X-generic deletes initramfs Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: Situation: linux-image-X-generic and linux-image-extra-X-generic are both installed When you remove linux-image-extra-X-generic (e.g. switching from -generic to -virtual) /boot/initrd.img-X-generic is deleted in linux-image-extra-X-generic's postrm script. This results into broken boot. At least when / is on LVM etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375310/+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 1375310] Re: Removing linux-image-extra-X-generic deletes initramfs
The fix of running all the kernel-post-install hooks on removal of a linux-image-extra package causes another bug (#1440608) with the autoremoval feature. Please see my comment on https://bugs.launchpad.net/bugs/1440608 . -- 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/1375310 Title: Removing linux-image-extra-X-generic deletes initramfs Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Bug description: Situation: linux-image-X-generic and linux-image-extra-X-generic are both installed When you remove linux-image-extra-X-generic (e.g. switching from -generic to -virtual) /boot/initrd.img-X-generic is deleted in linux-image-extra-X-generic's postrm script. This results into broken boot. At least when / is on LVM etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375310/+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 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one Status in apt package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: After installing a 3rd kernel currently 3.19.0-12-generic, the /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the 3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to be autoremoved. But once autoremove is completed the machine requests to be rebooted and at that time the /etc/apt/apt.conf.d /01autoremove-kernels file lists the 3.19.0-12-generic and 3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is requested to be autoremoved leaving only one kernel the latest one 3.19.0-12-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 5 17:03:01 2015 InstallationDate: Installed on 2015-04-02 (3 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+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 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one
The problem is that on purge/removal the linux-image-extra package runs all the kernel post-*install*-hooks in /etc/kernel/postinst.d (as its postrm hook), including the /etc/kernel/postinst.d/apt-auto-removal hook. The 'to-be-removed'-version of the kernel is given as an argument and thereby added to the list /etc/apt/apt.conf.d/01autoremove-kernels of kernels which shall not be autoremoved. Which at this point is clearly wrong, since we are probably just right now removing the respective kernel (linux-image) version as well. This bug was introduced as a fix to #1375310 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1375310). A fix is not so obvious for me, as running some /etc/kernel/postinst.d/ hooks might be required upon removal of a specific version of the linux- extra-image, if the corresponding linux-image package is not going to be removed. But just running blindly all kernel-postinst hooks on removal of a package does not really seem like a good idea to me. Regards, Robert. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1440608 Title: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one Status in apt package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After installing a 3rd kernel currently 3.19.0-12-generic, the /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the 3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to be autoremoved. But once autoremove is completed the machine requests to be rebooted and at that time the /etc/apt/apt.conf.d /01autoremove-kernels file lists the 3.19.0-12-generic and 3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is requested to be autoremoved leaving only one kernel the latest one 3.19.0-12-generic. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 5 17:03:01 2015 InstallationDate: Installed on 2015-04-02 (3 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+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
