ibmvfc_tgt_a..._cancel_done(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ibmvfc_tgt_a..._cancel_done(9)

okay so bestie, welcome to the Kernel API Manual, section 9 — aka the deep-lore corner of the kernel docs where the function names are long and the vibes are immaculate. Today's main character is ibmvfc_tgt_a..._cancel_done (yes the name is truncated with ... in the header, that's just how it's printed, don't come for her 🎀).

✨ NAME ✨

ibmvfc_tgt_adisc_cancel_done — the completion handler you call when you're cancelling an ADISC. that's it, that's the whole job. 🦋

🌸 SYNOPSIS 🌸

void ibmvfc_tgt_adisc_cancel_done (struct ibmvfc_event *evt );

🎀 ARGUMENTS 🎀

  • evt — the ibmvfc event struct. the little event guy in question. she's the star of the show. ⭐

💖 DESCRIPTION 💖

okay so the way this works is adorably simple: this handler is just here to cleanup this event struct. literally that's it. everything else? handled by the ADISC completion handler. she does not need to do the emotional labor, she just tidies up her own stuff and leaves the rest to the professionals. 💅

but here's the plot twist 😭 — if the ADISC never actually comes back, we still have the timer running on the ADISC event struct, and that timer will fire and cause the CRQ to get reset. so like, worst case scenario it self-rescues. no cap, that's the safety net.

👑 SEE ALSO 👑

these are all in the kernel file ./drivers/scsi/ibmvscsi/ibmvfc-core.c, and honestly? the whole friend group. slay. 🫶

quick vibe check 💖 — the source lives at ./drivers/scsi/ibmvscsi, dated October 2026, and that's genuinely the whole page. ty for coming to my ted talk, ily, bye bestie 🧚✨💜
📦 where this page comes from