linux-kernel - Re: [BUG? NVME Linux-4.15] Dracut loops indefinitely with 4.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPVZMnp6XbRfmEAU=6GwXO3VswQYr0Jkvwf6qvzPQm0k+pjrOQ@mail.gmail.com>
Date:   Thu, 15 Feb 2018 22:42:16 +0100
From:   Julien Durillon <julien@...illon.xyz>
To:     Keith Busch <keith.busch@...el.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [BUG? NVME Linux-4.15] Dracut loops indefinitely with 4.15

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