Hi, On Thu, Mar 02, 2023 at 12:47:53PM +0100, Guillem Jover wrote: > Hi! > > On Thu, 2023-03-02 at 12:12:06 +0100, Paul Gevers wrote: > > Control: fixed -1 5.10.162-1 6.1.8-1 > > > On Sun, 21 Aug 2022 21:35:58 +0200 Bastian Blank <wa...@debian.org> wrote: > > > On Sun, Aug 21, 2022 at 07:42:10PM +0200, Guillem Jover wrote: > > > > It seems like there was a regression with the latest stable update > > > > that affects the autopkgtest for liburing. Reassigning. > > > > > > Please provide enough information to make isolating the problem > > > possible. > > > > > > https://ci.debian.net/packages/libu/liburing/ is completely silent as > > > there are not results for any of the failed runs. > > > I decided to try again to see if I could collect more information. The test > > now passes on amd64, arm64, i386 and ppc64el, all running 5.10.162-1 and on > > riscv64 running unstable. However, on armhf, armel (amd64 kernel) and s390x > > (all running 5.10.158-2), it seems that the observation of brian is still > > true, some test in test-unit test segfaults, the test exits and hangs. > > @Guillem, do you see something more in the output below (armhf log) that may > > be of interest? And maybe spot something to run in isolation? > > > Reading the changelog of 5.10.162-1 I see io_uring mentioned a couple of > > times. Therefor I assume this bug is fixed in that version. Is it worth > > pursuing the real issue here? > > Thanks for looking into this! As this appears fixed in latest Linux > releases, then I'd honestly not bother further, and just try to get the > remaining hosts upgraded to the fixed versions. If this was to reappear > then it might make sense to look into it again.
FWIW, it is correct, the 5.10.162 release upstream was basically the one to bring the io_uring implementation inline with 5.15.y series (with the io_uring codebase from 5.15.85). So would agree, it make sense to update all remaining hosts and then look into it again in case the problem arise again. Regards, Salvatore
