Speaking for myself and not the SRU team as a whole, I think this issue has reached the level of complexity to analyse effectively that it's not worth doing an SRU given: 1) the risk to existing, unaffected users, including the risk that analysis has missed something; and 2) the theoretical bug issue that remains, that nobody else has hit since Noble's release, once the sysctl workaround has been tweaked and that requires a very unusual set of circumstances to replicate.
To be clear, I think Wesley's analysis is excellent given the complexity involved. But it is a complex area, and with that complexity comes risk, which is why we try not to make deep changes in stable releases. I'll leave it for other SRU team members to reach their own conclusions, and then I guess we'll need to make a collective decision. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168803 Title: QEMU 8.2.2 guests crash by exhausting vm.max_map_count with coroutines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2168803/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
