From: syzbot <syzbot+1d51c8b74efa4c44adeb@syzkaller.appspotmail.com>
To: ap420073@gmail.com, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: proc registration bug in snmp6_register_dev
Date: Wed, 06 May 2020 02:42:05 -0700 [thread overview]
Message-ID: <000000000000b0077705a4f79399@google.com> (raw)
In-Reply-To: <000000000000ea641705a350d2ee@google.com>
syzbot has bisected this bug to:
commit e0a4b99773d3d8d3fb40087805f8fd858a23e582
Author: Taehee Yoo <ap420073@gmail.com>
Date: Fri Feb 28 18:02:10 2020 +0000
hsr: use upper/lower device infrastructure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14811182100000
start commit: ac935d22 Add linux-next specific files for 20200415
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16811182100000
console output: https://syzkaller.appspot.com/x/log.txt?x=12811182100000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc498783097e9019
dashboard link: https://syzkaller.appspot.com/bug?extid=1d51c8b74efa4c44adeb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148e6150100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=115c379c100000
Reported-by: syzbot+1d51c8b74efa4c44adeb@syzkaller.appspotmail.com
Fixes: e0a4b99773d3 ("hsr: use upper/lower device infrastructure")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-05-06 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 9:20 WARNING: proc registration bug in snmp6_register_dev syzbot
2020-05-05 14:32 ` Taehee Yoo
2020-05-06 3:11 ` syzbot
2020-05-06 9:42 ` 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=000000000000b0077705a4f79399@google.com \
--to=syzbot+1d51c8b74efa4c44adeb@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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.