lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 20 Mar 2019 15:58:40 +0000
From:   Jon Maloy <jon.maloy@...csson.com>
To:     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

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.

///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")

Powered by blists - more mailing lists