nvme cli utility clips Leaf model # to 20 characters

[bugproxy]

nvme cli only shows the first 20 characters of the Leaf model number (mn) i.e "PCIe3 3.2TB NVMe Fla"
    root@gdx1x152:~# nvme id-ctrl /dev/nvme0 | more
      NVME Identify Controller:
      vid : 0x1c58
      ssvid : 0x1014
      sn : CJH001001830
      mn : PCIe3 3.2TB NVMe Fla
      fr : KMIPP107

When I check data from lspci it shows correct name
      Product Name: PCIe3 3.2TB NVMe Flash Adapter

checking block device data also shows correct model name
      # cat /sys/block/nvme0n1/device/model
      PCIe3 3.2TB NVMe Flash Adapter
      #

== Comment: #5 - Guilherme Guaglianoni Piccoli - 2016-06-21 16:07:02 ==
Not too much commits between v0.5 and v0.7. The following 2 commits are the fix to this issue:

ab43012 ("Fix the bug of Model Number and display the info of Serial Number")
a304435 ("Fix the bug of Model Number and display the info of Serial Number")

Probably the 1st was merged too early, instead of waiting v2..so it's easier to backport both, in order.

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvme-cli - 0.7-1ubuntu1

---------------
nvme-cli (0.7-1ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.
    - Includes upstream fix for truncated Leaf model number (LP: #1595274).
  * Remaining changes:
    - fix segfault when using show-regs command with no device
      name
    - fix null pointer deference segfault on strcmp() on a
      null string

nvme-cli (0.7-1) unstable; urgency=medium

  * New upstream release
  * Bump Standard-Version to 3.9.8, no changes required.

 -- Steve Langasek <email address hidden> Thu, 23 Jun 2016 12:45:21 -0700

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-07-28 08:27 EDT-------
I want to ask Canonical is there's any news on the backport of the aforementioned patches to Xenial's nvme-cli.

Thanks in advance,

Guilherme

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-08-26 17:27 EDT-------
.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-09-30 13:45 EDT-------
Hello Canonical.

What is the status on the request to backport this to xenial?

Thanks.

[Brian Murray (brian-murray)]

Hello bugproxy, or anyone else affected,

Accepted nvme-cli into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvme-cli/0.5-1ubuntu0.1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-10-28 09:29 EDT-------
Verification done using the proposed package.
Thanks very much Canonical.

[Launchpad Janitor (janitor)]

This bug was fixed in the package nvme-cli - 0.5-1ubuntu0.1

---------------
nvme-cli (0.5-1ubuntu0.1) xenial; urgency=medium

  * d/p/0001-Fix-the-bug-of-Model-Number-and-display-the-info-of-.patch,
    d/p/0002-Fix-the-bug-of-Model-Number-and-display-the-info-of-.patch:
    cherry-pick patches from upstream to fix display of information for
    devices with long names. LP: #1595274.

 -- Steve Langasek <email address hidden> Mon, 17 Oct 2016 17:21:59 -0700

[Chris J Arges (arges)]

The verification of the Stable Release Update for nvme-cli has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.