On Thu, 2020-08-20 at 11:47 +0200, Jason A. Donenfeld wrote: > On Wed, Aug 19, 2020 at 8:42 PM syzbot > <syzbot+cc4c0f394e2611edba66@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > syzbot has bisected this issue to: > > > > commit e7096c131e5161fa3b8e52a650d7719d2857adfd > > Author: Jason A. Donenfeld <Jason@xxxxxxxxx> > > Date: Sun Dec 8 23:27:34 2019 +0000 > > > > net: WireGuard secure network tunnel > > > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175ad8b1900000 > > start commit: e3ec1e8c net: eliminate meaningless memcpy to data in pskb.. > > git tree: net-next > > final oops: https://syzkaller.appspot.com/x/report.txt?x=14dad8b1900000 > > console output: https://syzkaller.appspot.com/x/log.txt?x=10dad8b1900000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=3d400a47d1416652 > > dashboard link: https://syzkaller.appspot.com/bug?extid=cc4c0f394e2611edba66 > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d9de91900000 > > > > Reported-by: syzbot+cc4c0f394e2611edba66@xxxxxxxxxxxxxxxxxxxxxxxxx > > Fixes: e7096c131e51 ("net: WireGuard secure network tunnel") > > Having trouble linking this back to wireguard... Those oopses don't > have anything to do with it either. Bisection error? Probably the typical generic netlink issue - syzbot often hits the generic netlink family by ID, rather than by name. So when it has a kernel without WG a generic netlink family disappears, the later ones get different IDs, and the issue no longer happens since the ID is now no longer valid or hitting some completely different code path ... johannes
