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

[Brian Murray]

Hello Kleber, or anyone else affected,

Accepted debian-installer into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu543.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: debian-installer (Ubuntu Bionic)
       Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
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 at 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 at redhat.com>
  Signed-off-by: Keith Busch <keith.busch at intel.com>
  Reviewed-by: Christoph Hellwig <hch at lst.de>
  Signed-off-by: Jens Axboe <axboe at kernel.dk>

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