The reasoning behind that can be found in bug #720095. Basically vsftp was found to be one case of using NET_NS and the way network namespaces work in 2.6.32 they can be quickly created but take an awful long time on teardown. So a quick sequence of cloning a process with a new network namespace and ending it quickly can be used to make a system run out of memory.
The behaviour is much better in 2.6.35, but the code was massively changed in between. So trying to bring that back to .32 would end up in porting most of the network changes. We cannot do this in a stable release without risking regressions. So it is either leaving a potential OOM vector open or to disable the support. The LTS-backports kernels are supposed to be close the gap between needing new kernel functionality but staying at the LTS release. What exactly were the "more problems" that were encountered and in which kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
