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
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 89C9B5AE
sudo apt-add-repository -u 'http://ubuntu.repo.uni-hannover.de/ubuntu xenial
Or get the key from here:
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40
Status in linux package in Ubuntu:
Status in linux source package in Xenial:
Status in linux source package in Yakkety:
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
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
Wat was expected:
$UID in autofs map are substituted by the uid of the user that starts the
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
---- Additional info ----
Description: Ubuntu 16.04.1 LTS
USER PID ACCESS COMMAND
/dev/snd/controlC0: run00001 3015 F.... pulseaudio
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-09-19 (10 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
enp0s8 no wireless extensions.
enp0s3 no wireless extensions.
lo no wireless extensions.
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)
PATH=(custom, no user)
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
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.
Uname: Linux 4.4.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: innotek GmbH
dmi.board.vendor: Oracle Corporation
dmi.chassis.vendor: Oracle Corporation
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp