http://bugzilla.suse.com/show_bug.cgi?id=1095096 http://bugzilla.suse.com/show_bug.cgi?id=1095096#c20 Johannes Thumshirn <jthumshirn@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jthumshirn@suse.c | |om) | --- Comment #20 from Johannes Thumshirn <jthumshirn@suse.com> --- (In reply to Franck Bui from comment #18)

OK so I think the problem here is due to the replacement of the old compat rule dealing with nvme devices which used scsi_id.

But since the scsi translation for nvme devices was depecrated in the kernel, we switched the code to use sysfs attributes only.

@Johannes according to you this was a safe switch but apparently we obtain a different result here:

For the devices we have this still holds true: zen2:~ # cat /sys/class/nvme/nvme0/serial CVFT71340019800MGN zen2:~ # /usr/lib/udev/scsi_id --whitelisted --replace-whitespace -d /dev/nvme0n1 SNVMe_INTEL_SSDPEDMD80CVFT71340019800MGN

- scsi_id returns the following serial id "200080d03000c85f8", see comment #17.

- OTOH the new rule[1] using sysfs attributes returns something totally different: "SNVMe_THNSN5512GPUK NV17BB502BKSHU", see the value of "ID_NVME_SERIAL_COMPAT" returned by the output of "udevadm info" in comment #9.

Can you see what's going wrong here ?

[1] The new rule looks like this:

...

KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}!="?*", ATTRS{model}=="?*", ATTRS{serial}=="?*", \ PROGRAM=="/bin/sh -c ' \ cd /sys/%p; \ while ! [ -f model ]; do \ cd ..; \ [ $(pwd) = %S ] && exit 1; \ done; \ cut -c 1-16 model'", ENV{ID_NVME_SERIAL_COMPAT}="SNVMe_%c%s{serial}"

KERNEL=="nvme*", ENV{DEVTYPE}=="disk", ENV{ID_NVME_SERIAL_COMPAT}=="?*", SYMLINK+="disk/by-id/nvme-$env{ID_NVME_SERIAL_COMPAT}"

This looks correct to me. So the device is answering different things to the old ioctl and the new sysfs paths -- You are receiving this mail because: You are on the CC list for the bug.