[Bug 1789227] Re: nvme devices namespace assigned to the wrong controller

No regression here (tested ubuntu-server daily on x86 VM)

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Tags removed: verification-needed
** Tags added: verification-done

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1789227

Title:
nvme devices namespace assigned to the wrong controller

Status in debian-installer package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in debian-installer source package in Bionic:
Fix Committed
Status in linux source package in Bionic:
Fix Released

Bug description:
== Impact ==

During device discovery, when multipath is disabled, nvme multipath
module will very likely think that the name space on one nvme
controller belongs to the other controller.


== Fix ==

Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream

From: Keith Busch <keith.busch@intel.com>

When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath,
namespaces with multiple paths were not creating unique names due to
reusing the same instance number from the namespace's head.

This patch fixes this by falling back to the non-multipath naming method
when the parameter disabled using multipath.

Reported-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1789227/+subscriptions