This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed- trusty'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1649635 Title: export nvme drive model/serial strings via sysfs (trusty) Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Fix Committed Bug description: [Impact] Without the model and serial strings for each nvme drive exported via sysfs, udev cannot create the /dev/disk/by-id/ symlinks, since it can't access the model/serial info. Without these symlinks, it's difficult to uniquely identify a specific nvme drive. [Test Case] The udev rules to create the nvme symlinks need updating, per bug 1642903 and bug 1647485. With the udev package updated with fixes/workarounds from those bugs, boot a kernel without this patch on a system with nvme drive(s), and check the /dev/disk/by-id/ directory; no symlinks to the nvme drives should be present. With this kernel patch, check the directory, and symlinks to all nvme drives and their partitions should be present, in the form of /dev/disk/by-id/nvme- MODEL_SERIAL for the drive and /dev/disk/by-id/nvme-MODEL_SERIAL-partN for each partition. [Regression Potential] Creating/managing sysfs files can result in problems ranging from memory leaks to a kernel oops, if not managed correctly. [Other Info] This functionality is present in upstream kernels, but the change diff between this kernel version and where this functionality appears upstream is massive - the driver changes from manually managing its userspace access over to using the standard device infrastructure, as well as numerous other bugfixes and feature changes. So instead of attempting to backport all those changes, this patch retains only a small part of the upstream patch and adds direct sysfs file creation using device_create_file(), which the upstream code never did. This is by far the simplest way to update this very old kernel with the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1649635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
