From: syzbot <syzbot+1b4ebf4dae4e510dd219@syzkaller.appspotmail.com>
To: davem@davemloft.net, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
petrm@mellanox.com, syzkaller-bugs@googlegroups.com,
yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in erspan_netlink_parms
Date: Mon, 16 Mar 2020 00:49:02 -0700 [thread overview]
Message-ID: <00000000000081b1df05a0f40d13@google.com> (raw)
In-Reply-To: <000000000000c08f2005a0ed60d4@google.com>
syzbot has bisected this bug to:
commit e1f8f78ffe9854308b9e12a73ebe4e909074fc33
Author: Petr Machata <petrm@mellanox.com>
Date: Fri Mar 13 11:39:36 2020 +0000
net: ip_gre: Separate ERSPAN newlink / changelink callbacks
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101477fde00000
start commit: 0fda7600 geneve: move debug check after netdev unregister
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=121477fde00000
console output: https://syzkaller.appspot.com/x/log.txt?x=141477fde00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c2e311dba9a02ba9
dashboard link: https://syzkaller.appspot.com/bug?extid=1b4ebf4dae4e510dd219
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1627f955e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111ac52de00000
Reported-by: syzbot+1b4ebf4dae4e510dd219@syzkaller.appspotmail.com
Fixes: e1f8f78ffe98 ("net: ip_gre: Separate ERSPAN newlink / changelink callbacks")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-16 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 23:51 general protection fault in erspan_netlink_parms syzbot
2020-03-16 7:49 ` syzbot [this message]
2020-03-16 17:00 ` Petr Machata
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=00000000000081b1df05a0f40d13@google.com \
--to=syzbot+1b4ebf4dae4e510dd219@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).