lpfc_nvmet_xmt_ls_abort_cmp(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 lpfc_nvmet_xmt_ls_abort_cmp — Kernel API Manual, section 9 🎀

okay so bestie, we're diving into the Kernel API Manual today and the star of the show is lpfc_nvmet_xmt_ls_abort_cmp 💅 this is a kernel-level function so put your serious face on (but keep the sparkle) ✨

👑 NAME

lpfc_nvmet_xmt_ls_abort_cmp — the completion handler for ABTS 🫶

✨ SYNOPSIS

void lpfc_nvmet_xmt_ls_abort_cmp (struct lpfc_hba *phba , struct
lpfc_iocbq *cmdwqe , struct lpfc_iocbq *rspwqe );

that's the whole signature, no cap, copy it exactly the way it is 💖

🎀 ARGUMENTS

  • phba — a pointer to the HBA context object, aka the main character of this whole hardware situation 👑
  • cmdwqe — a pointer to the driver command WQE object, the request side of things 🦋
  • rspwqe — a pointer to the driver response WQE object, the reply side, its other half fr fr 🌸

💜 DESCRIPTION

so here's the vibe check: this function gets called from the SLI ring event handler, and — important detail — it's called with no lock held 🔥 like, none. zero. head empty, no locks. keep that in mind.

it's the completion handler for NVME ABTS for LS cmds ✨ (yes, that's the exact phrasing, we don't water it down). and what does it actually do? it frees the memory resources that were being used for the NVME commands 💀 like a little cleanup fairy, doing the tidying so nothing leaks 🧚

🌈 SEE ALSO

first up, the kernel file this whole thing lives in:

./drivers/scsi/lpfc/lpfc_nvmet.c

and then the whole friend group — literally all of these, go say hi 👋

💡 friendly reminder: no locks held when this runs. that's not me being extra, that's just the truth of it, bestie 🫶

and that's a wrap, babe 🎀 this page came to you from the ./drivers/scsi/lpfc directory, dated October 2026, printed by the Kernel API Manual as page lpfc_nvmet_xmt_ls_abort_cmp(9) — slay, go free some memory, ily ⭐💖

📦 where this page comes from