This one identifies the same culprit as [email protected], but points to a different bug. That bug has also been fixed, in commit adba75be0d23 ("tipc: fix lockdep warning when reinitilaizing sockets"), applied in 4.20 but not present in 4.16, - the source of the dump. Once again, a dump from 4.20/5.0 might be a help.
///jon > -----Original Message----- > From: syzbot <[email protected]> > Sent: 18-Mar-19 08:28 > To: [email protected]; Jon Maloy <[email protected]>; > [email protected]; [email protected]; > [email protected]; [email protected]; tipc- > [email protected]; [email protected]; yoshfuji@linux- > ipv6.org > Subject: Re: general protection fault in fib6_purge_rt > > syzbot has bisected this bug to: > > commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81 > Author: Jon Maloy <[email protected]> > Date: Thu Mar 22 19:42:52 2018 +0000 > > tipc: obtain node identity from interface by default > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1116d2a3200000 > start commit: 52dfae5c tipc: obtain node identity from interface by defa.. > git tree: linux-next > final crash: https://syzkaller.appspot.com/x/report.txt?x=1316d2a3200000 > console output: https://syzkaller.appspot.com/x/log.txt?x=1516d2a3200000 > kernel config: https://syzkaller.appspot.com/x/.config?x=c8b6073d992e8217 > dashboard link: > https://syzkaller.appspot.com/bug?extid=a25307ad099309f1c2b9 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b2c56f200000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b8890b200000 > > Reported-by: [email protected] > Fixes: 52dfae5c ("tipc: obtain node identity from interface by default") _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
