It does seem like this must be a kernel bug in epoll+signalfd (or a hard to spot misuse thereof in lxc).
When I instrument the signal_handler which is executed when epoll_wait returns a signalfd event, I do get a sigchld for the very first task which is spawned (a test to see if kernel supports pidns reboot), but do not get one for the container init - which becomes <defunct> and therefore clearly did in fact send a sigchld. I'll send my tiny patch upstream, and test on other kernels for comparison. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1168526 Title: race condition causing lxc to not detect container init process exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1168526/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
