lpfc_discovery_wait(9)

💫 lpfc_discovery_wait(9) 💫

okay so bestie, welcome to the Kernel API Manual entry for lpfc_discovery_wait — yes, that's the function name and also the whole vibe of this page. let's get into it 🎀

---

✨ NAME ✨

lpfc_discovery_wait — wait for driver discovery to quiesce. literally just sit there and let discovery chill out before you do anything else 💅

---

🌸 SYNOPSIS 🌸

void lpfc_discovery_wait (struct lpfc_vport *vport );

---

🦋 ARGUMENTS 🦋

• vport — the virtual port for which this call is being executed. that's it, that's the whole argument, she's lowkey simple like that 🫶

---

👑 DESCRIPTION 👑

so this driver calls this routine specifically from lpfc_vport_delete to enforce a synchronous execution of vport delete relative to discovery activities. like, the delete has to line up with discovery and wait its turn, no cutting the queue bestie 😭

the lpfc_vport_delete routine should not return until it can reasonably guarantee that discovery has quiesced. that's the whole point — delete does not get to dip until discovery is actually done.

post FDISC LOGO, the driver must wait until its SAN teardown is complete and all resources recovered before allowing cleanup. so after the FDISC LOGO situation, it's giving "we are not leaving until the SAN teardown is finished and every resource is recovered," periodt 🔥

this routine does not require any locks held. no lock drama, no extra setup, she's self-sufficient like that 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/scsi/lpfc/lpfc_vport.c

---

and that's the page, bestie! this iconic little number lives in ./drivers/scsi/lpfc and the version/date moment is October 2026, with the manual page name being lpfc_discovery_wait(9) — so yeah, that's the whole sign-off: source ./drivers/scsi/lpfc, dated October 2026, page lpfc_discovery_wait(9) 🧚💜