From: Waiman Long <longman@redhat.com>
To: syzbot <syzbot+499aea72daa2cea73cb7@syzkaller.appspotmail.com>,
benh@kernel.crashing.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, 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 12:20:14 -0400 [thread overview]
Message-ID: <db670b70-8ed9-94d5-6492-622a8e0bf28b@redhat.com> (raw)
In-Reply-To: <00000000000066c5a605a366e88c@google.com>
#syz fix: locking/lockdep: Reuse freed chain_hlocks entries
prev parent reply other threads:[~2020-04-16 16:20 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
2020-04-16 16:20 ` Waiman Long [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=db670b70-8ed9-94d5-6492-622a8e0bf28b@redhat.com \
--to=longman@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=syzbot+499aea72daa2cea73cb7@syzkaller.appspotmail.com \
--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).