[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+anbSEh89LaFeT2Bi4qVM1Maf_0x11ynrfCk9PNvg9UXw@mail.gmail.com>
Date: Wed, 20 Mar 2019 17:41:01 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Jon Maloy <jon.maloy@...csson.com>
Cc: syzbot <syzbot+a25307ad099309f1c2b9@...kaller.appspotmail.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuznet@....inr.ac.ru" <kuznet@....inr.ac.ru>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
"tipc-discussion@...ts.sourceforge.net"
<tipc-discussion@...ts.sourceforge.net>,
"ying.xue@...driver.com" <ying.xue@...driver.com>,
"yoshfuji@...ux-ipv6.org" <yoshfuji@...ux-ipv6.org>
Subject: Re: general protection fault in fib6_purge_rt
On Wed, Mar 20, 2019 at 4:59 PM Jon Maloy <jon.maloy@...csson.com> wrote:
>
> This one identifies the same culprit as syzbot+9d4c12bfd45a58738d0a@...kaller.appspotmail.com, 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.
Looking at the bisection log maybe this reproducer triggers multiple
kernel bugs.
All crashes including the latest ones and other info are always
available on the dashboard.
> ///jon
>
>
> > -----Original Message-----
> > From: syzbot <syzbot+a25307ad099309f1c2b9@...kaller.appspotmail.com>
> > Sent: 18-Mar-19 08:28
> > To: davem@...emloft.net; Jon Maloy <jon.maloy@...csson.com>;
> > kuznet@....inr.ac.ru; linux-kernel@...r.kernel.org;
> > netdev@...r.kernel.org; syzkaller-bugs@...glegroups.com; tipc-
> > discussion@...ts.sourceforge.net; ying.xue@...driver.com; yoshfuji@...ux-
> > ipv6.org
> > Subject: Re: general protection fault in fib6_purge_rt
> >
> > syzbot has bisected this bug to:
> >
> > commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
> > Author: Jon Maloy <jon.maloy@...csson.com>
> > 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@...kaller.appspotmail.com
> > Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@...glegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/BL0PR1501MB20039998B662DCC11E2B38D79A410%40BL0PR1501MB2003.namprd15.prod.outlook.com.
> For more options, visit https://groups.google.com/d/optout.
Powered by blists - more mailing lists