[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
Problem still exists in Ubuntu 16.10. ** Summary changed: - starting any container with umask 007 breaks lxc-stop and prevents host system shutdown + starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
I reproduced it with the latest mainline kernel as well: Linux xenialbox 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20 22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Here's the slightly different syslog output: Nov 22 14:36:55 xenialbox kernel: [ 484.506570] INFO: task systemd:3086 blocked for more than 120 seconds. Nov 22 14:36:55 xenialbox kernel: [ 484.506578] Not tainted 4.9.0-040900rc6-generic #201611201731 Nov 22 14:36:55 xenialbox kernel: [ 484.506579] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 22 14:36:55 xenialbox kernel: [ 484.506582] systemd D0 3086 3076 0x0104 Nov 22 14:36:55 xenialbox kernel: [ 484.506589] 8eaa1810bc00 8eaa58f4d800 8eaa57f59d00 8eaa5fc19340 Nov 22 14:36:55 xenialbox kernel: [ 484.506593] 8eaa54bec880 9bab80f17b78 8bc87183 8c244480 Nov 22 14:36:55 xenialbox kernel: [ 484.506596] 00ff8eaa57f59d00 8eaa5fc19340 8eaa57f59d00 Nov 22 14:36:55 xenialbox kernel: [ 484.506600] Call Trace: Nov 22 14:36:55 xenialbox kernel: [ 484.506622] [] ? __schedule+0x233/0x6e0 Nov 22 14:36:55 xenialbox kernel: [ 484.506626] [] schedule+0x36/0x80 Nov 22 14:36:55 xenialbox kernel: [ 484.506629] [] rwsem_down_write_failed+0x20a/0x380 Nov 22 14:36:55 xenialbox kernel: [ 484.506634] [] ? kvm_sched_clock_read+0x1e/0x30 Nov 22 14:36:55 xenialbox kernel: [ 484.506643] [] ? kernfs_sop_show_options+0x40/0x40 Nov 22 14:36:55 xenialbox kernel: [ 484.506651] [] call_rwsem_down_write_failed+0x17/0x30 Nov 22 14:36:55 xenialbox kernel: [ 484.506655] [] down_write+0x2d/0x40 Nov 22 14:36:55 xenialbox kernel: [ 484.506658] [] grab_super+0x30/0xa0 Nov 22 14:36:55 xenialbox kernel: [ 484.506661] [] sget_userns+0x18f/0x4d0 Nov 22 14:36:55 xenialbox kernel: [ 484.506663] [] ? kernfs_sop_show_path+0x50/0x50 Nov 22 14:36:55 xenialbox kernel: [ 484.50] [] kernfs_mount_ns+0x7e/0x230 Nov 22 14:36:55 xenialbox kernel: [ 484.506674] [] cgroup_mount+0x328/0x840 Nov 22 14:36:55 xenialbox kernel: [ 484.506679] [] ? alloc_pages_current+0x95/0x140 Nov 22 14:36:55 xenialbox kernel: [ 484.506682] [] mount_fs+0x38/0x150 Nov 22 14:36:55 xenialbox kernel: [ 484.506686] [] vfs_kern_mount+0x67/0x110 Nov 22 14:36:55 xenialbox kernel: [ 484.506688] [] do_mount+0x1e1/0xcb0 Nov 22 14:36:55 xenialbox kernel: [ 484.506691] [] ? __check_object_size+0xff/0x1d6 Nov 22 14:36:55 xenialbox kernel: [ 484.506695] [] ? kmem_cache_alloc_trace+0xd7/0x190 Nov 22 14:36:55 xenialbox kernel: [ 484.506697] [] SyS_mount+0x83/0xd0 Nov 22 14:36:55 xenialbox kernel: [ 484.506700] [] do_syscall_64+0x5b/0xc0 Nov 22 14:36:55 xenialbox kernel: [ 484.506702] [] entry_SYSCALL64_slow_path+0x25/0x25 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
Linux xenialbox 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
This sounds like a kernel bug to me. Can you please provide the output of: uname -a and try to reproduce this on a newer kernel version and report back? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: - If I run lxc-start with umask 007 (or any other value that masks the - world-execute bit), my host system enters a state with the following - problems: + If I have umask 007 (or any other value that masks the world-execute + bit) when I run lxc-start for the first time after logging in, my host + system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. - * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. + * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully-updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. + I can reproduce this at will with a freshly-installed and fully-updated + host OS in VirtualBox, and with either an old-ish container or a new + one. + I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. - - I can reproduce this at will with a freshly installed host OS in - VirtualBox, and with either an old-ish container or a new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. - I can reproduce this at will with either an old-ish container or a fresh - new one. + I can reproduce this at will with a freshly installed host OS in + VirtualBox, and with either an old-ish container or a new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
Possibly related: when the problem is triggered, I notice that my guest instances start with no /etc/resolv.conf and no inet address. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
