public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	"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: Mon, 27 Jun 2022 23:18:58 -0700	[thread overview]
Message-ID: <YrqdUpLVbLF7WNGs@infradead.org> (raw)
In-Reply-To: <Yrqb47ozk5IWTnWp@kroah.com>

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.

  reply	other threads:[~2022-06-28  6:19 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 [this message]
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=YrqdUpLVbLF7WNGs@infradead.org \
    --to=hch@infradead.org \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox