From: syzbot <syzbot+a25307ad099309f1c2b9@syzkaller.appspotmail.com>
To: davem@davemloft.net, jon.maloy@ericsson.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com,
yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in fib6_purge_rt
Date: Mon, 18 Mar 2019 00:28:00 -0700 [thread overview]
Message-ID: <00000000000010f4270584595484@google.com> (raw)
In-Reply-To: <000000000000dbe73a057cd65da2@google.com>
syzbot has bisected this bug to:
commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
Author: Jon Maloy <jon.maloy@ericsson.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@syzkaller.appspotmail.com
Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")
next prev parent reply other threads:[~2019-03-18 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 17:17 general protection fault in fib6_purge_rt syzbot
2019-03-12 18:49 ` syzbot
2019-03-18 7:28 ` syzbot [this message]
2019-03-20 15:58 ` Jon Maloy
2019-03-20 16:41 ` Dmitry Vyukov
2019-03-20 16:53 ` Jon Maloy
2019-03-20 19:08 ` Xin Long
2019-03-21 8:53 ` Jon Maloy
2019-03-21 12:40 ` Xin Long
2019-03-21 13:55 ` Jon Maloy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000010f4270584595484@google.com \
--to=syzbot+a25307ad099309f1c2b9@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.