Comment # 23 on bug 1189776 from Franck Bui

These symlinks in /sys/dev/block, used by udevadm to find the actual device and
that point to devices in /sys/devices/virtual/nvme-subsystem, are actually the
problem because none of the paths below nvme-susbsystem  has the "driver"
attribute.

My VM running TW with an emulated nvme device has the symlinks in
/sys/dev/block
pointing to the "real" device instead:

# ls -l /sys/dev/block/
total 0
lrwxrwxrwx 1 root root 0 Oct 13 14:59 259:0 ->
../../devices/pci0000:00/0000:00:06.0/nvme/nvme0/nvme0n1
lrwxrwxrwx 1 root root 0 Oct 13 14:59 259:1 ->
../../devices/pci0000:00/0000:00:06.0/nvme/nvme0/nvme0n1/nvme0n1p1

and paths below /sys/devices/pci0000:00/0000:00:06.0 do have the "driver"
attribute.

Now I don't know why the kernel sometimes chooses the paths below
/sys/device/virtual/nvme-susbsystem and sometimes it prefers /sys/devives/pci*
but the interface exposed to userspace doesn't seem consistent and reliable.

Jean, could you shed some light please ?