From: hujunwei <hujunwei4@huawei.com>
To: syzbot <syzbot+01dd5c4b3c34a5cf9308@syzkaller.appspotmail.com>,
<davem@davemloft.net>, <jon.maloy@ericsson.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<syzkaller-bugs@googlegroups.com>,
<tipc-discussion@lists.sourceforge.net>, <ying.xue@windriver.com>
Subject: Re: BUG: spinlock bad magic in rhashtable_walk_enter
Date: Fri, 24 May 2019 10:53:24 +0800 [thread overview]
Message-ID: <7da38946-ae8f-93bf-99c3-28949eb46354@huawei.com> (raw)
In-Reply-To: <0000000000003df61e05899887d3@google.com>
On 2019/5/24 9:58, syzbot wrote:
> 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=17c22c72a00000
> start commit: 510e2ced ipv6: fix src addr routing with the exception table
> git tree: net
> final crash: https://syzkaller.appspot.com/x/report.txt?x=14222c72a00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10222c72a00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=82f0809e8f0a8c87
> dashboard link: https://syzkaller.appspot.com/bug?extid=01dd5c4b3c34a5cf9308
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b6373ca00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1251e73ca00000
>
> Reported-by: syzbot+01dd5c4b3c34a5cf9308@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
>
> .
>
This bug was fixed by:
commit 526f5b851a96 (" tipc: fix modprobe tipc failed after switch order of device registration")
Regards,
Junwei
prev parent reply other threads:[~2019-05-24 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 7:28 BUG: spinlock bad magic in rhashtable_walk_enter syzbot
2019-05-24 1:58 ` syzbot
2019-05-24 2:53 ` hujunwei [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=7da38946-ae8f-93bf-99c3-28949eb46354@huawei.com \
--to=hujunwei4@huawei.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+01dd5c4b3c34a5cf9308@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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 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).