pci_hp_spurious_link_change(9)

💖 pci_hp_spurious_link_change 💖

okay bestie, welcome to the Kernel API Manual entry for pci_hp_spurious_link_change — yes, that whole mouthful is the title, and we’re gonna make it make sense. ✨

🌸 NAME 🌸

pci_hp_spurious_link_change — check for spurious link changes. periodt. 💅

✨ SYNOPSIS ✨

bool pci_hp_spurious_link_change (struct pci_dev *pdev );

🎀 ARGUMENTS 🎀

• pdev — the PCI hotplug bridge. That’s the bridge we’re checking for spurious link change drama, no cap. 🦋

🦋 DESCRIPTION 🦋

Okay so here’s the vibe: this function checks whether a code section is executing concurrently that is causing spurious link changes on the Secondary Bus of pdev. If that code section is running, it awaits the end of the code section. Lowkey polite of it. 🫶

Hotplug drivers may call this to check whether a link change is spurious and can be ignored.

⚠️ Important caveat, bestie: because a genuine link change may have occurred in-between a spurious link change and the invocation of this function, hotplug drivers should perform sanity checks — such as retrieving the current link state and bringing down the slot if the link is down. Do not just trust the vibe check alone. 😭

💖 RETURN 💖

• Returns true if such a code section has been executing concurrently; otherwise false.
• Also returns true if such a code section has not been executing concurrently, but at least once since the last invocation of this function. Yes, it’s giving “remembering the last time” energy. ✨

👑 SEE ALSO 👑

• Kernel file ./drivers/pci/hotplug/pci_hotplug_core.c
• __pci_hp_register(9)
• __pci_hp_initialize(9)
• pci_hp_add(9)
• pci_hp_deregister(9)
• pci_hp_del(9)
• pci_hp_destroy(9)
• pci_hp_ignore_link_change(9)
• pci_hp_unignore_link_change(9)

That’s the whole page, no cap. Big slay sign-off: this one lives under ./drivers/pci/hotplug, dated October 2026, in the pci_hp_spurious_link_change(9) manual. 💅✨🎀