Page MenuHomeFreeBSD

pci: Only add special VF handling for direct children in bus methods
ClosedPublic

Authored by jhb on Jun 5 2024, 3:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Feb 14, 9:57 AM
Unknown Object (File)
Jan 1 2025, 3:45 AM
Unknown Object (File)
Dec 31 2024, 3:35 AM
Unknown Object (File)
Dec 30 2024, 4:07 AM
Unknown Object (File)
Dec 29 2024, 4:46 AM
Unknown Object (File)
Dec 28 2024, 2:51 AM
Unknown Object (File)
Dec 27 2024, 12:49 PM
Unknown Object (File)
Dec 26 2024, 10:52 AM
Subscribers
None

Details

Summary

For activate/deactivate resource, use a more standard check at the
start of the function since the addition of the PCI_IOV code made this
more complex. For the three recently added methods, just add the
typical check at the beginning that I missed.

This wasn't always fatal as if your system only had PCI device_t's as
children of PCI bus devices it would happen to work ok, but if you
have a non-PCI child device (e.g. an ATA channel) then dereferencing
ivars for non-direct-children could fault.

Reported by: Cirrus-CI (via emaste)
Fixes: 871b33ad65ba pci: Consistently use pci_vf_* for suballocated VF memory resources

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable