summaryrefslogtreecommitdiffstats
path: root/drivers/pci
diff options
context:
space:
mode:
authorLu Baolu <baolu.lu@linux.intel.com>2024-02-27 03:14:41 +0100
committerJoerg Roedel <jroedel@suse.de>2024-03-01 13:51:21 +0100
commitdef054b01a867822254e1dda13d587f5c7a99e2a (patch)
tree5d2c0eca919c6caa0e759d9dc93f79078e07d76a /drivers/pci
parentiommu/vt-d: Use rbtree to track iommu probed devices (diff)
downloadlinux-def054b01a867822254e1dda13d587f5c7a99e2a.tar.xz
linux-def054b01a867822254e1dda13d587f5c7a99e2a.zip
iommu/vt-d: Use device rbtree in iopf reporting path
The existing I/O page fault handler currently locates the PCI device by calling pci_get_domain_bus_and_slot(). This function searches the list of all PCI devices until the desired device is found. To improve lookup efficiency, replace it with device_rbtree_find() to search the device within the probed device rbtree. The I/O page fault is initiated by the device, which does not have any synchronization mechanism with the software to ensure that the device stays in the probed device tree. Theoretically, a device could be released by the IOMMU subsystem after device_rbtree_find() and before iopf_get_dev_fault_param(), which would cause a use-after-free problem. Add a mutex to synchronize the I/O page fault reporting path and the IOMMU release device path. This lock doesn't introduce any performance overhead, as the conflict between I/O page fault reporting and device releasing is very rare. Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Link: https://lore.kernel.org/r/20240220065939.121116-3-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/pci')
0 files changed, 0 insertions, 0 deletions