Page MenuHomeFreeBSD

pci: Don't try to read cfg registers of non-existing devices
ClosedPublic

Authored by kd on Nov 19 2021, 7:54 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 20, 2:08 AM
Unknown Object (File)
Sat, Apr 13, 6:35 PM
Unknown Object (File)
Tue, Apr 9, 2:01 AM
Unknown Object (File)
Sat, Mar 30, 1:35 AM
Unknown Object (File)
Wed, Mar 27, 7:12 PM
Unknown Object (File)
Mar 21 2024, 3:13 AM
Unknown Object (File)
Mar 21 2024, 3:13 AM
Unknown Object (File)
Mar 21 2024, 3:13 AM
Subscribers
None

Details

Summary

Instead of returning 0xffs some controllers, such as Layerscape generate an external exception when someone attempts to read any register of config space of a non-existing device other than PCIR_VENDOR.
This causes a kernel panic.
Fix it by bailing during device enumeration if a device vendor register returns invalid value. (0xffff)
Use this opportunity to replace some hardcoded values with a macro.

I believe that this change won't have any unintended side-effects since it is safe to assume that if vendor == 0xffff -> hdr_type == 0xffff,
which means that we won't accidentally skip enumerating a slot.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

kd requested review of this revision.Nov 19 2021, 7:54 AM
kd created this revision.

Huh, interesting that the newer code (rescan) DTRT.

sys/dev/pci/pci.c
686

While this is fine, we should arguably assert that this never happens as I think we should be catching this case in all the callers? Hmm, I guess we expose this for use by CardBus, so perhaps it is best left as you have changed it. I would be happy if we could check all the callers and assert here instead though, perhaps as a followup.

4145–4147

Just add a blank line before the new comment.

This revision is now accepted and ready to land.Nov 22 2021, 5:58 PM