From: Keith Busch <keith.busch@intel.com>
To: Julien Durillon <julien@durillon.xyz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG? NVME Linux-4.15] Dracut loops indefinitely with 4.15
Date: Thu, 15 Feb 2018 13:19:20 -0700 [thread overview]
Message-ID: <20180215201919.GA7076@localhost.localdomain> (raw)
In-Reply-To: <CAPVZMnqi0dF1u=Q223trP=mtvYd80Ydp5wamtz3Vt3xhRY-FEQ@mail.gmail.com>
On Thu, Feb 15, 2018 at 02:49:56PM +0100, Julien Durillon wrote:
> I opened an issue here:
> https://github.com/dracutdevs/dracut/issues/373 for dracut. You can
> read there how dracuts enters an infinite loop.
>
> TL;DR: in linux-4.14, trying to find the last "slave" of /dev/dm-0
> ends with a maj:min of "249:0" which does not exist in /sys/dev/block.
> In linux-4.15, the same thing loops as "249:0" exists.
The problem is dracut assumes the 'dev' file for an nvme namespace's
parent device contains a maj:min for a block device. It's actually a
character device, and its maj:min happens to also be be the same as the
device mapper's block device.
next prev parent reply other threads:[~2018-02-15 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:49 [BUG? NVME Linux-4.15] Dracut loops indefinitely with 4.15 Julien Durillon
2018-02-15 20:19 ` Keith Busch [this message]
2018-02-15 21:42 ` Julien Durillon
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=20180215201919.GA7076@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=julien@durillon.xyz \
--cc=linux-kernel@vger.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