Bug#1032104: linux: ppc64el iouring corrupted read
> > On Sat, Mar 18, 2023 at 11:19:29PM -0700, Otto Kekäläinen wrote:
> > > Any updates on this one?
> > >
> > > I am still seeing the main.index_merge_innodb failure in
> > > https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1678728871&raw=0
> > > and rebuild https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64el&ver=1%3A10.11.2-2%7Eexp1&stamp=1679174850&raw=0.
> > >
> > > Logs show: Kernel: Linux 5.10.0-21-powerpc64le #1 SMP Debian
> > > 5.10.162-1 (2023-01-21) ppc64el (ppc64le)
> >
> > Remember that with the 5.10.162 upstream version the io_uring code was
> > rebased to the 5.15-stable one. So it is likely, and it maches the
> > verison ranges, that the regression was introduced with this
> > particular changes. Ideally someone with access to the given
> > architecture, can verify that the issue is gone with the current
> > 5.10.175 upstream (where there were several followup fixes, in
> > particular e.g. a similar one for s390x), and if not, reports the
> > problem to upstream.
> >
> > Paul Gevers asked if the issues are gone as well with 6.1.12-1
> > (or later 6.1.y series versions, which will land in bookworm). That
> > would be valuable information to know as well to exclude we do not
> > have the issue as well in bookworm.
>
> Were you able to verify this?
No, not yet.
I have not done new uploads to experimental after the one I mentioned
and linked above from March 18th.
The builds for unstable are passing because I forced the tests to run
with regular fsync instead of native I/O in
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/fc1358087b39ac6520420c7bbae2e536bc86748d.
I will test this again later but right now I don't want to do any
extra uploads as the package is pending unblock and inclusion in
Bullseye (Bug#1033811) and I don't want one single minor issue to
jeopardize getting fixes for multiple major issues forward.
Reply to: