On Sun, Jul 31, 2022 at 2:53 AM Willy Tarreau <w@xxxxxx> wrote: > > Thus I'm a bit confused about what to look for. It's very likely that > there are still bugs left in this driver, but trying to identify them > and to validate a fix will be difficult if they cannot be reproduced. > Maybe they only happen under emulation due to timing issues. > > As such, any hint about the exact setup and how long to wait to get > the error would be much appreciated. We can confirm that we were able to trigger the issue on the latest 5.19 (commit: 3d7cb6b04c3f3115719235cc6866b10326de34cd) with the C-repro within a VM. We use this: https://syzkaller.appspot.com/text?tag=KernelConfig&x=cd73026ceaed1402 config to build the kernel. The issue triggers after around 143 seconds. For all the five times we tried, we were able to reproduce the issue deterministically every time. Please let us know if you need any other information. -- Thanks and Regards, Dipanjan
