Ok - thanks - I was able to reproduce this in a raring VM with 4 cores. I thought this might be a tiny race window between us blocking signals and creating the signalfd, so I reversed those (a patch which I may yet send upstream) - but that didn't solve the issue.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
