From: syzbot <syzbot+6440134c13554d3abfb0@syzkaller.appspotmail.com>
To: davem@davemloft.net, hujunwei4@huawei.com,
jon.maloy@ericsson.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, wangxiaogang3@huawei.com,
ying.xue@windriver.com
Subject: Re: WARNING: locking bug in rhashtable_walk_enter
Date: Tue, 21 May 2019 14:08:00 -0700 [thread overview]
Message-ID: <00000000000071c8a105896c3ef2@google.com> (raw)
In-Reply-To: <000000000000ac9447058924709c@google.com>
syzbot has bisected this bug to:
commit 7e27e8d6130c5e88fac9ddec4249f7f2337fe7f8
Author: Junwei Hu <hujunwei4@huawei.com>
Date: Thu May 16 02:51:15 2019 +0000
tipc: switch order of device registration to fix a crash
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1285d39ca00000
start commit: f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1185d39ca00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1685d39ca00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc045131472947d7
dashboard link: https://syzkaller.appspot.com/bug?extid=6440134c13554d3abfb0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c586bca00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14759fb2a00000
Reported-by: syzbot+6440134c13554d3abfb0@syzkaller.appspotmail.com
Fixes: 7e27e8d6130c ("tipc: switch order of device registration to fix a
crash")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-05-21 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 7:28 WARNING: locking bug in rhashtable_walk_enter syzbot
2019-05-21 21:08 ` syzbot [this message]
2019-05-22 13:38 ` 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=00000000000071c8a105896c3ef2@google.com \
--to=syzbot+6440134c13554d3abfb0@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=hujunwei4@huawei.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=wangxiaogang3@huawei.com \
--cc=ying.xue@windriver.com \
/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.