Hi Lance, I haven’t seen this problem before. Does this system have multiple NVMe devices, and only one (or a subset) of them has driver_override set? I notice that the two examples you gave were both for PCI BDF 40:00.0 – I assume that means this was collected on two different systems? https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-pci seems to indicate that something must be writing “nvme” to that file – i.e. it’s not done internally by the kernel. Maybe our setup.sh script should at least check for this – i.e. don’t reset driver_override to (null) but print a warning message if it finds it set to “nvme”. -Jim From: SPDK <spdk-bounces(a)lists.01.org&gt; on behalf of Lance Hartmann ORACLE <lance.hartmann(a)oracle.com&gt; Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org&gt; Date: Tuesday, June 26, 2018 at 10:17 AM To: Storage Performance Development Kit <spdk(a)lists.01.org&gt; Subject: [SPDK] Debugging /sys driver_override affecting driver binding During my experimentation of unbinding NVMe controllers from the Linux nvme driver and then binding them to vfio-pci for use with SPDK, I encountered unusual behavior with one of the controllers. For some, initially inexplicable, reason, one of the NVMe controllers did get unbound as desired from the nvme driver, but it refused to bind to vfio-pci, whereas all the other NVMe controllers had no trouble at all binding to vfio-pci. Inspection of the kernel log (dmesg) didn’t help. And so after a bunch of debugging I uncovered the culprit: the /sys driver attribute, driver_override. By default, all of my NVMe controller’s appeared to have that attribute empty/null, e.g.: # cat /sys/bus/pci/devices/0000:40:00.0/driver_override (null) However, I discovered that for the NVMe controller that refused to bind to vfio-pci, its driver_override attribute contained the string “nvme”: # cat /sys/bus/pci/devices/0000:40:00.0/driver_override nvme Per Linux kernel documentation, ABI/testing/sysfs-bus-pci: This file allows the driver for a device to be specified which will override standard static and dynamic ID matching. When specified, only a driver with a name matching the value written to driver_override will have an opportunity to bind to the device. … Eureka! So, that explains why I had a particular NVMe device that refused to bind to vfio-pci. I wanted to share this discovery with other folks in case that run into a similar issue. Now, the mystery that remains: how and why did this particular NVMe controller get its driver_override attribute set to “nvme”? It’s not being used as boot device, I’ve never attempted to use it with LVM (Linux Logical Volume Management), nor built any file systems on it, or any such thing. I grep’d through both my real rootfs’s /etc and searched through my initramfs as well, but I’ve yet to discover what’s responsible for setting that particular NVMe controller’s driver_override. Anyone have some ideas? thanks, -- Lance Hartmann lance.hartmann@oracle.com<mailto:lance.hartmann@oracle.com>

<snip> https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-pci seems to indicate that something must be writing “nvme” to that file – i.e. it’s not done internally by the kernel. Maybe our setup.sh script should at least check for this – i.e. don’t reset driver_override to (null) but print a warning message if it finds it set to “nvme”. I agree completely, but so far my find/grep (for strings “override” and "30:00.0”) has failed to locate the source; again, neither below my real rootfs’s /etc nor anywhere on my initramfs. I also checked my kernel cmdline. The mystery continues. Like you, I was also considering modifying the SPDK’s scripts/setup.sh to inspect driver_override and at least put out some kind of message if the contents is not “(null)”. One of my colleagues here suggested using ftrace to see what process is setting the driver_override. Can you add “ftrace=function ftrace_filter=driver_override_store” to your kernel command line? Then after booting, just “cat /sys/kernel/debug/tracing/trace”. -Jim