linux-kernel - [5.3.*] nvme issue

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-next>] [day] [month] [year] [list]

Message-ID: <7f230245-a999-1cf3-fce5-d68a41b13d17@xs4all.nl>
Date:   Sat, 19 Oct 2019 13:22:30 +0200
From:   Udo van den Heuvel <udovdh@...all.nl>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [5.3.*] nvme issue

Linux-guru's,

When I boot this workstation, the nvme disks appear in /dev/ without
their partitions. fdisk shows there are partitions but cannot write a
new partitions table,  mentions a busy disk.
These processes are busy with the nvme disks:

root       236     2  0 13:08 ?        00:00:00 [nvme-wq]
root       237     2  0 13:08 ?        00:00:00 [nvme-reset-wq]
root       238     2  0 13:08 ?        00:00:00 [nvme-delete-wq]

If I kill these, (re)write a partition table the partitions appear in
/dev/ and can be used.

How do I prevent this situation from occurring? I want my partitions
visible.

(fedora 30, kernel 5.3.7, etc, etc)

Also: a `make install` of the kernel does not put the current
/etc/crypttab in the ramdisk. How to force this so that the crypttab is
updated?

Kind reghards,
Udo