I added a task for systemd to consider raising the default
RLIMIT_MEMLOCK limit.
This upstream commit raises the default limit to 8Mb:
https://github.com/systemd/systemd/commit/852b62507b2
The way things are now, the following scenario does NOT work out of the
box:
- jammy lxd on focal host
-
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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: test failure due to low memlock limit
To manage
On uring and memlock:
https://git.kernel.dk/cgit/liburing/tree/README#n19
--
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: test failure due to low memlock limit
To manage
Ok, after some experimenting and code inspection, this is the summary.
This is the logic that decides if mariadb 10.6.7 will try to use uring or not,
AT RUNTIME:
bool innodb_use_native_aio_default()
{
#ifdef HAVE_URING
utsname = uname_for_io_uring;
if (!uname() && u.release[0] == '5' &&
