Thanks for the further checks Lena! With that tested and confirmed I think we can rest assured about general Archive breakage - as there is none to be had so far except if there is a hidden RSEQ user we missed to look at.
And the really affected library (full tcmalloc) isn't shipped in Ubuntu either. For general awareness we might mention it in the release notes still, but I'd not see the messaging as a regression because as it seems all it did was getting stricter on an API - so it isn't really a bug (We can leave the discussion between kernel and tcmalloc to them). OTOH the kernel changes thousands of things every time and what is in the archive we try to smoothen and hold compatible. But we do not list all potential and theoretical things out there that could have issues. The only difference here is that it was brought to our attention. But the kernel did nothing wrong nor is something in the Ubuntu archive affected. I'm unsure but IMHO this thereby would come down a) do nothing b) to a kernel related release note entry like "FYI Kernel got stricter, nothing in the archive is affected, but if you use code relying on that wrong behavior you might see issues - known is for example this issue in tcmalloc [link]" WDYT? At least this is clearly less urgent or widespread of a problem than it first looked. Let us talk about the next steos next time we meet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146842 Title: tcmalloc RSEQ ABI violation causes crashes on linux kernel 6.19+ To manage notifications about this bug go to: https://bugs.launchpad.net/pkg-google-perftools/+bug/2146842/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
