RE: general protection fault in fib6_purge_rt

From: Jon Maloy
Date: Wed Mar 20 2019 - 11:59:08 EST


This one identifies the same culprit as syzbot+9d4c12bfd45a58738d0a@xxxxxxxxxxxxxxxxxxxxxxxxx, 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 <syzbot+a25307ad099309f1c2b9@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Sent: 18-Mar-19 08:28
> To: davem@xxxxxxxxxxxxx; Jon Maloy <jon.maloy@xxxxxxxxxxxx>;
> kuznet@xxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> netdev@xxxxxxxxxxxxxxx; syzkaller-bugs@xxxxxxxxxxxxxxxx; tipc-
> discussion@xxxxxxxxxxxxxxxxxxxxx; ying.xue@xxxxxxxxxxxxx; yoshfuji@linux-
> ipv6.org
> Subject: Re: general protection fault in fib6_purge_rt
>
> syzbot has bisected this bug to:
>
> commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
> Author: Jon Maloy <jon.maloy@xxxxxxxxxxxx>
> 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: syzbot+a25307ad099309f1c2b9@xxxxxxxxxxxxxxxxxxxxxxxxx
> Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")