From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Christoph Hellwig <hch@infradead.org>,
"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 17:12:48 +0100 [thread overview]
Message-ID: <20210401161248.GA1510273@infradead.org> (raw)
In-Reply-To: <2d76014e-1e78-0ea9-e661-e441334f7897@acm.org>
On Thu, Apr 01, 2021 at 09:09:53AM -0700, Bart Van Assche wrote:
> 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.
We've seen a similar trace a while ago, and back then decided not to
fix it given that it is harmless and pktcdvd was considered to be on the
way out. But it seems like systemd now tries to set up pktcdvd?
_______________________________________________
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:29 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
2021-04-01 16:12 ` Christoph Hellwig [this message]
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=20210401161248.GA1510273@infradead.org \
--to=hch@infradead.org \
--cc=bvanassche@acm.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