(In reply to Michael Catanzaro from comment #76) > We wound up not reverting the patches. > > aarch64 is still broken (bug #209670), but ppc64le is now fine. > > Solving bug #209670 is basically impossible. We are being expected to > provide a value at compile time that cannot be known until runtime. Very > frustrating. > > Oh, and I discovered people are actually using huge pages, so WebKit is > guaranteed to be broken for them no matter what. *shrug!*
One way around this is to disable this mitigation for those platforms that cannot be statically configured: basically, on those platforms, at runtime, check if page size is within acceptable limits (and whatever other criteria you need), and if not, disable the mitigation and don’t do the page freeze. On platforms that can guarantee their page sizes, this option to disable the mitigation should be #if’d out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868108 Title: [autopkgtest][focal] ruby-gnome/3.4.1-2build1 class:TestWebKit2GtkWebView failure To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1868108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
