On Sun, Jan 10, 2021 at 10:34 PM syzbot <syzbot+5f326d255ca648131...@syzkaller.appspotmail.com> wrote: > > syzbot suspects this issue was fixed by commit: > > commit 537cf4e3cc2f6cc9088dcd6162de573f603adc29 > Author: Magnus Karlsson <magnus.karls...@intel.com> > Date: Fri Nov 20 11:53:39 2020 +0000 > > xsk: Fix umem cleanup bug at socket destruct > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=139f3dfb500000 > start commit: e87d24fc Merge branch 'net-iucv-fixes-2020-11-09' > git tree: net > kernel config: https://syzkaller.appspot.com/x/.config?x=61033507391c77ff > dashboard link: https://syzkaller.appspot.com/bug?extid=5f326d255ca648131f87 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d10006500000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126c9eaa500000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: xsk: Fix umem cleanup bug at socket destruct > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
FTR, the bisection log looks clean, but this does not look like the fix for this. The reproducer does not destroy sockets.
