Moving over to the kernel as a userspace process shouldn't be able to
cause such a hang regardless of what it does so this looks like a kernel
bug (lock related by the looks of it).
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member
I'm running umask 027 (set in `.bashrc` for my user, which is copied to
my root session after using `su`) and can report this issue still occurs
for unprivileged containers under Debian 9 (stretch, stable) using LXC
2.0.7-2+deb9u2 and kernel 4.19.0-0.bpo.4-amd64. I can also confirm umask
at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
My previous comment is unclear, the two problems are:
1. 'lxc' directories below '/sys/fs/cgroup/' are created according to
the umask setting
2. then mounting '/sys/fs/cgroup/systemd' in the container hangs (and
attempts to reboot or shut down the host system fail, a hard reset is
required).
I was able to reproduce this bug on Debian unstable (lxc=2.0.7-2,
libpam-cgfs=2.0.6-1, systemd=232-22, linux-image-4.9.0-2-amd64=4.9.18-1
or even using 4.11.0-rc6-1, libpam-cgm not installed, cgmanager not
installed) with Debian Jessie unprivileged container (created using
download template [1]).
5 matches
Mail list logo
