Hello,
there is a
[ 0.579232] pci 0000:00:00.2: Resources present before probing
error message observed after
commit 3be5fa236649da6404f1bca1491bf02d4b0d5cce
Author: Lukas Wunner <lukas@xxxxxxxxx>
Date: Fri Apr 25 11:24:21 2025 +0200
Revert "iommu/amd: Prevent binding other PCI drivers to IOMMU PCI devices"
After tracking this down I've found that it's agpgart-amd64 driver trying
to bind to the IOMMU device:
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h-19h IOMMU
Subsystem: Lenovo Device 3803
Flags: bus master, fast devsel, latency 0, IRQ 25
Capabilities: <access denied>
IOMMU device itself has no pci_driver attached to it but has a pci_dev,
and its struct device already has some devres associated with it.
agpgart-amd64 driver booting with 'agp_try_unsupported=1' (turns out it's
a default behavior) traverses the devices on the PCI bus and tries to
attach:
static const struct pci_device_id agp_amd64_pci_promisc_table[] = {
{ PCI_DEVICE_CLASS(0, 0) },
{ }
};
...
int __init agp_amd64_init(void)
{
...
/* Look for any AGP bridge */
agp_amd64_pci_driver.id_table = agp_amd64_pci_promisc_table;
err = driver_attach(&agp_amd64_pci_driver.driver);
if (err == 0 && agp_bridges_found == 0) {
pci_unregister_driver(&agp_amd64_pci_driver);
err = -ENODEV;
}
IOMMU device is busy at the moment but, to my mind, lack of pci_driver
associated with it leads driver core trying to bind it, too.
But registering a pci_driver for IOMMU device is no good.
Initial commit cbbc00be2ce3 ("iommu/amd: Prevent binding other PCI drivers
to IOMMU PCI devices") was added in 2015, not sure whether the problem
manifested before that. At least the commit message doesn't state that
it tried to fix such kind of a bug.
The problem on itself is no harm at the end as driver core handles the
error and skips the device. But it still indicates a logical bug.
The partial revert of the revert does work, obviously. Though it badly
contradicts the intention to hide priv_flags manipulation in the PCI core.
So I wonder whether agpgart-amd64 should be somehow fixed instead... to
skip IOMMU device from its wildcard promiscuous PCI ID table? Or drop this
'try_unsupported' feature entirely?
Would be glad to hear your thoughts on this.
Found by Linux Verification Center (linuxtesting.org).
--
Thanks,
Fedor
