qla_delete_n...ess_and_wait(9)

💅 qla_delete_n...ess_and_wait(9) — a Kernel API Manual moment ✨

okay so this is from the Kernel API Manual bestie, and it's genuinely such a specific little function 🎀 the name's literally truncated with dots in the header (qla_delete_n...ess_and_wait(9)) so like… that's just how it's filed, don't come for me 💀

---

🌸 NAME 🌸

qla_delete_n2n_sess_and_wait — it searches for an N2N session, tears it all the way down, and then waits for the teardown to actually finish. no cap, it waits. 🫶

and here's the lil context that matters: in N2N topology, there is only one session being active in tracking the remote device. one. single. main character session 👑 so yeah, that's the whole vibe.

---

✨ SYNOPSIS ✨

int qla_delete_n2n_sess_and_wait (scsi_qla_host_t *vha );

literally the whole signature, character for character, copy-pasted energy but make it cute 🦋

---

🎀 ARGUMENTS 🎀

• vha — the host adapter pointer 💖 and yes, the return code lives right here in the argument blurb (iykyk), so here's the tea:
  • 0 — it found the session and completed the tear down 🎉 slay.
  • 1 — timeout occurred 😭 the caller is supposed to use a link bounce to reset it. fr fr, that's the recovery plan.

bestie this is NOT ambiguous: 0 = found + torn down, 1 = timeout, caller does a link bounce. those are the only two outcomes listed. periodt 💅

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/scsi/qla2xxx/qla_edif.c — and like, the whole friend group:

• qla_edif_app_check(9)
• qla_edif_app_start(9)
• qla_edif_app_stop(9)
• qla_edif_app_authok(9)
• qla_edif_app_authfail(9)
• qla_edif_app_getfcinfo(9)
• qla_edif_app_getstats(9)
• qla_enode_init(9)
• qla_enode_stop(9)
• qla_pur_get_pending(9)
• qla28xx_start_scsi_edif(9)

all eleven of them, in order, no skips 🌈 go read them too, they're iconic.

---

k bye ily, this page came from ./drivers/scsi/qla2xxx and it's dated October 2026 — stamped on qla_delete_n...ess_and_wait(9) 💜 see u in the next manpage bestie 🧚