Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <20180215201919.GA7076@localhost.localdomain>
References: <CAPVZMnqi0dF1u=Q223trP=mtvYd80Ydp5wamtz3Vt3xhRY-FEQ@mail.gmail.com>
 <20180215201919.GA7076@localhost.localdomain>
From:   Julien Durillon <julien@durillon.xyz>
Date:   Thu, 15 Feb 2018 22:42:16 +0100
Message-ID: <CAPVZMnp6XbRfmEAU=6GwXO3VswQYr0Jkvwf6qvzPQm0k+pjrOQ@mail.gmail.com>
Subject: Re: [BUG? NVME Linux-4.15] Dracut loops indefinitely with 4.15
To:     Keith Busch <keith.busch@intel.com>
Cc:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

2018-02-15 21:19 GMT+01:00 Keith Busch <keith.busch@intel.com>:
> 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.

So dracut should see that it's a character device and not a block device?

-- 
Julien Durillon