From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Recursive locking complaint with nvme-5.13 branch
Date: Thu, 1 Apr 2021 09:09:53 -0700 [thread overview]
Message-ID: <2d76014e-1e78-0ea9-e661-e441334f7897@acm.org> (raw)
In-Reply-To: <20210401153722.GA1501960@infradead.org>
On 4/1/21 8:37 AM, Christoph Hellwig wrote:
> On Wed, Mar 31, 2021 at 09:03:36PM -0700, Bart Van Assche wrote:
>> If I boot a VM with the nvme-5.13 branch (commit 24e238c92186
>> ("nvme: warn of unhandled effects only once")) then the complaint
>> shown below is reported. Is this a known issue?
>
> This looks like someone is trying to open a nvme device as the backing
> device for pktcdvd? In that case this is a different bd_mutex. But
> I'm really curious why systemd would do that.
Hi Christoph,
This call trace was reported during boot. The configuration of the VM
that reported this call trace is as follows:
- Boot from a virtio disk.
- One SATA CD-ROM.
- One SATA disk.
- One IDE disk.
- One SCSI disk.
- No NVMe controller since virt-manager does not support NVMe
controllers as far as I know.
I reported this call trace to the linux-nvme mailing list instead of
linux-block since I haven't seen this call trace yet with Jens' for-next
branch.
Please let me know if you need more information.
Bart.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-01 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 4:03 Recursive locking complaint with nvme-5.13 branch Bart Van Assche
2021-04-01 15:37 ` Christoph Hellwig
2021-04-01 16:09 ` Bart Van Assche [this message]
2021-04-01 16:12 ` Christoph Hellwig
2021-04-01 17:20 ` Bart Van Assche
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=2d76014e-1e78-0ea9-e661-e441334f7897@acm.org \
--to=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.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