From: syzbot <syzbot+499aea72daa2cea73cb7@syzkaller.appspotmail.com>
To: benh@kernel.crashing.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, longman@redhat.com,
mingo@kernel.org, peterz@infradead.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
torvalds@linux-foundation.org
Subject: Re: WARNING in kernfs_new_node
Date: Thu, 16 Apr 2020 04:41:04 -0700 [thread overview]
Message-ID: <00000000000066c5a605a366e88c@google.com> (raw)
In-Reply-To: <000000000000e15ee0058f5dfa81@google.com>
syzbot suspects this bug was fixed by commit:
commit 810507fe6fd5ff3de429121adff49523fabb643a
Author: Waiman Long <longman@redhat.com>
Date: Thu Feb 6 15:24:08 2020 +0000
locking/lockdep: Reuse freed chain_hlocks entries
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=177d726fe00000
start commit: 1e78030e Merge tag 'mmc-v5.3-rc1' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e397351d2615e10
dashboard link: https://syzkaller.appspot.com/bug?extid=499aea72daa2cea73cb7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111d80fc600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d9060c600000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: locking/lockdep: Reuse freed chain_hlocks entries
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-04-16 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:38 WARNING in kernfs_new_node syzbot
2019-08-06 5:23 ` Benjamin Herrenschmidt
2020-04-16 11:41 ` syzbot [this message]
2020-04-16 16:20 ` Waiman Long
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=00000000000066c5a605a366e88c@google.com \
--to=syzbot+499aea72daa2cea73cb7@syzkaller.appspotmail.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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).