From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"hch@infradead.org" <hch@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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, 19 Jul 2022 02:05:30 +0000 [thread overview]
Message-ID: <33e90f37-c201-9ac6-f65e-3646341dcc2c@fujitsu.com> (raw)
In-Reply-To: <20220705004809.6guf43xwjpq33smo@shindev>
On 2022/7/5 8:48, Shinichiro Kawasaki wrote:
> On Jun 27, 2022 / 23:18, Christoph Hellwig wrote:
>> On Tue, Jun 28, 2022 at 08:12:51AM +0200, Greg Kroah-Hartman wrote:
>>> Ah, so it's a fake PCI device, or is it a real one?
>>
>> Whatever the blktests configuration points to. But even if it is
>> "fake" that fake would come from the hypervisor.
>
> FYI, the WARN was observed with real PCI NVMe device also. I observed the WARN
> with v5.19-rc1 and still observe with v5.19-rc5. I'm not sure which version
> introduced the WARN.
>
> I once reported this failure, and shared with linux-pci list.
>
> https://lore.kernel.org/linux-block/20220614010907.bvbrgbz7nnvpnw5w@shindev/
>
Hi Shinichiro,
I wonder if the failure has been fixed? If so, could you tell me the fix
patch?
Best Regards,
Xiao Yang
next prev parent reply other threads:[~2022-07-19 2:05 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
2022-06-28 6:18 ` Christoph Hellwig
2022-07-05 0:48 ` Shinichiro Kawasaki
2022-07-19 2:05 ` yangx.jy [this message]
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=33e90f37-c201-9ac6-f65e-3646341dcc2c@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--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=shinichiro.kawasaki@wdc.com \
--cc=tj@kernel.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