From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
Tejun Heo <tj@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [bug report from blktests nvme/032] WARNING: possible circular locking dependency detected
Date: Tue, 28 Jun 2022 08:12:51 +0200 [thread overview]
Message-ID: <Yrqb47ozk5IWTnWp@kroah.com> (raw)
In-Reply-To: <YrqbNfF9uYMSwZ4V@infradead.org>
On Mon, Jun 27, 2022 at 11:09:57PM -0700, Christoph Hellwig wrote:
> On Tue, Jun 28, 2022 at 08:07:52AM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 28, 2022 at 04:03:55AM +0000, yangx.jy@fujitsu.com wrote:
> > > Hi everyone,
> > >
> > > Running blktests nvme/032 on kernel v5.19-rc2+ which enables
> > > CONFIG_LOCKDEP and CONFIG_PROVE_LOCKING triggered the below WARNING.
> >
> > What was happening when this trace was created? It looks like you were
> > manually removing a PCI device from the system through sysfs? Why would
> > blktests do that?
>
> To test how the block layer copes with the fact that the underlying
> device goes away.
Ah, so it's a fake PCI device, or is it a real one?
Anyway, it's a valid thing to do, I'll look at the report in a bit...
next prev parent reply other threads:[~2022-06-28 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 4:03 [bug report from blktests nvme/032] WARNING: possible circular locking dependency detected yangx.jy
2022-06-28 6:07 ` Greg Kroah-Hartman
2022-06-28 6:09 ` Christoph Hellwig
2022-06-28 6:12 ` Greg Kroah-Hartman [this message]
2022-06-28 6:18 ` Christoph Hellwig
2022-07-05 0:48 ` Shinichiro Kawasaki
2022-07-19 2:05 ` yangx.jy
2022-07-19 4:42 ` Shinichiro Kawasaki
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=Yrqb47ozk5IWTnWp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=hch@infradead.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yangx.jy@fujitsu.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.