From: syzbot <syzbot+1695af5ca559927e2db8@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, f.fainelli@gmail.com,
gbastien@versatic.net, idosch@mellanox.com, jiri@mellanox.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, petrm@mellanox.com,
sd@queasysnail.net, stephen@networkplumber.org,
syzkaller-bugs@googlegroups.com, willemb@google.com,
yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in sit_exit_batch_net
Date: Wed, 02 Oct 2019 17:39:01 -0700 [thread overview]
Message-ID: <000000000000cfb2cb0593f6cfad@google.com> (raw)
In-Reply-To: <0000000000001530e00593f47496@google.com>
syzbot has bisected this bug to:
commit ff92741270bf8b6e78aa885f166b68c7a67ab13a
Author: Jiri Pirko <jiri@mellanox.com>
Date: Mon Sep 30 09:48:15 2019 +0000
net: introduce name_node struct to be used in hashlist
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13719e33600000
start commit: c01ebd6c r8152: Use guard clause and fix comment typos
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=10f19e33600000
console output: https://syzkaller.appspot.com/x/log.txt?x=17719e33600000
kernel config: https://syzkaller.appspot.com/x/.config?x=6ffbfa7e4a36190f
dashboard link: https://syzkaller.appspot.com/bug?extid=1695af5ca559927e2db8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1156242b600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17253b19600000
Reported-by: syzbot+1695af5ca559927e2db8@syzkaller.appspotmail.com
Fixes: ff92741270bf ("net: introduce name_node struct to be used in
hashlist")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-10-03 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 21:50 general protection fault in sit_exit_batch_net syzbot
2019-10-03 0:39 ` syzbot [this message]
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=000000000000cfb2cb0593f6cfad@google.com \
--to=syzbot+1695af5ca559927e2db8@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gbastien@versatic.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@mellanox.com \
--cc=sd@queasysnail.net \
--cc=stephen@networkplumber.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willemb@google.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.