On Fri, 30 Jun 2023 at 12:11, Alexander Potapenko <glider@xxxxxxxxxx> wrote: > > On Fri, Jun 30, 2023 at 12:02 PM Ard Biesheuvel <ardb@xxxxxxxxxx> wrote: > > > > On Fri, 30 Jun 2023 at 11:53, Tetsuo Handa > > <penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On 2023/06/30 18:36, Ard Biesheuvel wrote: > > > > Why are you sending this now? > > > > > > Just because this is currently top crasher and I can reproduce locally. > > > > > > > Do you have a reproducer for this issue? > > > > > > Yes. https://syzkaller.appspot.com/text?tag=ReproC&x=12931621900000 works. > > > > > > > Could you please share your kernel config and the resulting kernel log > > when running the reproducer? I'll try to reproduce locally as well, > > and see if I can figure out what is going on in the crypto layer > > The config together with the repro is available at > https://syzkaller.appspot.com/bug?extid=828dfc12440b4f6f305d, see the > latest row of the "Crashes" table that contains a C repro. Could you explain why that bug contains ~50 reports that seem entirely unrelated? AIUI, this actual issue has not been reproduced since 2020?? > Config: https://syzkaller.appspot.com/text?tag=KernelConfig&x=ee5f7a0b2e48ed66 > Report: https://syzkaller.appspot.com/text?tag=CrashReport&x=1325260d900000 > Syz repro: https://syzkaller.appspot.com/text?tag=ReproSyz&x=11af973e900000 > C repro: https://syzkaller.appspot.com/text?tag=ReproC&x=163a1e45900000 > > The bug is reproducible for me locally as well (and Tetsuo's patch > makes it disappear, although I have no opinion on its correctness). What I'd like to do is run a kernel plus initrd locally in OVMF and reproduce the issue - can I do that without all the syzkaller machinery?
