[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrqauCHdcieF5+C7@kroah.com>
Date: Tue, 28 Jun 2022 08:07:52 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "yangx.jy@...itsu.com" <yangx.jy@...itsu.com>
Cc: Tejun Heo <tj@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
Jason Gunthorpe <jgg@...pe.ca>,
Leon Romanovsky <leon@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: Re: [bug report from blktests nvme/032] WARNING: possible circular
locking dependency detected
On Tue, Jun 28, 2022 at 04:03:55AM +0000, yangx.jy@...itsu.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?
thanks,
greg k-h
Powered by blists - more mailing lists