kpartx causes kernel oops when NVMe devices is not in blacklist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
multipath-tools (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
Trusty |
Fix Released
|
High
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
Users expecting to use multipath over NVMe device will notice hangs with any software attempting to use the device-mapper devices (/dev/dm-* or /dev/mapper/
[Test case]
1) Setup multipath over nvme. (should not be possible with the patch in)
2) Run kpartx -av /dev/dm-
[Regression Potential]
Minimal. This removes a theoretically valid use case of multipath devices using NVMe disks, which is not technically supported and leads to software hangs (and thus installs will not complete, and setting up multipath over NVMe post-install would hang).
This only affects nvme devices; so any storage device using the "nvme" naming would no longer be able to setup multipath even if technical specifications were to change sufficiently to support multipath over NVMe (or if some other device starts using this naming which isn't affected by the same limitations).
-----
When on bare metal uses NVMe devices - kpartx cause kernel oops.
http://
Also any tools which works with disks (e.g. fdisk, lsblk) hangs in D state (uninterruptible sleep) while trying to to read /dev/dm-X.
This bug is already described and fixed in upstream (http://
I made patches for trusty and xenial versions of multipath-tools.
Patches which fix issue is in attach.
Could you apply this patches please, at least for trusty version?
The attachment "trusty nvme blacklist" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]