> > >>> > > >>> 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. > > > > Kernel is commit e6bc8833d80f of https://github.com/google/kmsan/commits/master . > > That commit does not exist in that repo. Does it matter? Apologies for this mess. https://github.com/google/kmsan/commits/master is force-updated once a week to point to the latest release candidate with KMSAN-specific patches. Older releases are called e.g. kmsan-v6.4-rc7. Right now there's only one patch required to run torvalds/master with KMSAN (https://github.com/google/kmsan/commit/e6bc8833d80f). That patch will hit upstream in v6.5-rc1, after which I am going to switch syzbot to test upstream. For such a long-standing bug the exact version of KMSAN shouldn't matter.
