On failure, mysql will crash and sysbench will report a connection loss to the database.
[Regression Risk]
The fix touch some low level locking code, so there is always the risk that it introduces a problem on other platforms. However, this fix has been included in MariaDB since the 10.0.13 release in Aug, 2014 so it has had some real world testing.
I've verified that the following MariaDB issue also impacts MySQL: /mariadb. atlassian. net/browse/ MDEV-6615
https:/
[Impact]
Data corruption on arm64 (and maybe ppc64el?)
[Test Case]
Reproducibility varies across SoCs but, at least on one SoC, it reliably fails within seconds with these sysbench commands:
sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp prepare
sysbench --num-threads=128 --max-requests=0 --max-time=1000 --test=oltp run
On failure, mysql will crash and sysbench will report a connection loss to the database.
[Regression Risk]
The fix touch some low level locking code, so there is always the risk that it introduces a problem on other platforms. However, this fix has been included in MariaDB since the 10.0.13 release in Aug, 2014 so it has had some real world testing.