commit 9a29ad897c64de29af69970a69066746d7f1a31a
Author: Daniel Black <daniel@mariadb.org>
Date: Fri Aug 22 15:50:43 2025 +1000
MDEV-37411: re-enable AIO in Debian
Upstream in MDEV-36234, added the possibility of a
dual async-io stack, both libaio and liburing.
This can be controlled by the system variable
innodb_linux_aio, defaulting to auto. When run
in an environment where liburing isn't available
(container on old kernels, containers seccomp rules,
disable at the kernel leve, insufficent locked
resources, etc), its recommend by upstream and
advisable to fall back to libaio.
As such we'll need to link again to libaio by
adding libaio to the build dependences and using
an explicit WITH_AIO=ON as a cmake build flag.
In appreciation that launchpad, and potentially
salsa aren't sufficiently configured for parallel
mtr runs with libaio, or liburing, we surpress
those warnings in MTR.
Among the 9 debian patches available in version 1:11.8.3-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/mariadb.png){kind=link}