linux-kernel - Re: [PATCH v2] driver core: Check drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8B3127BD-2892-46D5-8EE9-C75D812466DB@nutanix.com>
Date: Tue, 14 Oct 2025 12:10:33 +0000
From: Vincent Liu <vincent.liu@...anix.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "dakr@...nel.org" <dakr@...nel.org>,
        "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>,
        "rafael@...nel.org" <rafael@...nel.org>,
        "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
        "linux-pci@...r.kernel.org"
	<linux-pci@...r.kernel.org>
Subject: Re: [PATCH v2] driver core: Check drivers_autoprobe for all added
 devices

On 14 Oct 2025, at 06:14, Greg KH <gregkh@...uxfoundation.org> wrote:

> What commit id does this fix? 

I am not entirely sure if there is a particular commit that causes this issue,
the device_attach call was added in pci/bus.c 58d9a38f6fac, and then the
device_add was removed in 4f535093cf8f6. At this point I think the
drivers_autoprobe stopped working because driver_attach that’s left in
pci_bus_add_device does not check for that.

The drivers_autoprobe check in base/bus.c has been there a long time 
since b8c5cec23d5c.

> What devices cause this to happen today that are seeing this issue?

I am observing this for hot-plugged PCIe devices and VFs.

> Should this be backported to older kernels?

I suppose not since this was not working for a long time?

Thanks,
Vincent