Public bug reported: == 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.bu...@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 <snit...@redhat.com> Signed-off-by: Keith Busch <keith.bu...@intel.com> Reviewed-by: Christoph Hellwig <h...@lst.de> Signed-off-by: Jens Axboe <ax...@kernel.dk> ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Fix Committed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789227 Title: nvme devices namespace assigned to the wrong controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs