From 5.12 kernel memory locked pages aren't needed - https://github.com/axboe/liburing/issues/246#issuecomment-816965961.
In #1969160 I tested the upcoming 10.6 release (probably next week sometime) for crashes in uring initialization failures and it didn't. Apart from some error log differences from ENOMEM, ENOSYS etc are handles the same way in the fallback. I haven't quite concluded how the 10.6.7 release is crashing at the moment. With https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.13/+bug/1952222 I assume the jammy kernel 5.15.0 has the right patches to make 5.15.0 safe despite the MariaDB code not distinguishing it as so (suggestions of improving kernel version detection welcome). ** Bug watch added: github.com/axboe/liburing/issues #246 https://github.com/axboe/liburing/issues/246 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970634 Title: FTBFS: mariadb fails to start due to low MEMLOCK limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
