lpfc_nvme_un..._issue_abort(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lpfc_nvme_unsol_ls_issue_abort β€” bestie's guide to the kernel API manual ✨

okay so this is a page from the Kernel API Manual, and the function it's hyping up is lpfc_nvme_unsol_ls_issue_abort πŸŽ€ (the title gets abbreviated as lpfc_nvme_un..._issue_abort(9) in the corner, iykyk). buckle up, we're going into the driver ✨


🌸 NAME 🌸

lpfc_nvme_unsol_ls_issue_abort β€” the move where you fire off an ABTS on an exchange that got received through async frame receive, but like… the frame wasn't handled πŸ™ˆ so somebody's gotta abort it, and that somebody is this function, periodt.


πŸ¦‹ SYNOPSIS πŸ¦‹

int lpfc_nvme_unsol_ls_issue_abort (struct lpfc_hba *phba , struct lpfc_async_xchg_ctx *ctxp , uint32_t sid , uint16_t xri );

she returns an int, she takes four args, she's literally doing the most πŸ’…


✨ ARGUMENTS ✨

  • phba β€” pointer to the adapter structure 🫢 like, the whole HBA vibe, the main character
  • ctxp β€” pointer to the asynchronously received sequence (the manual says "received received", and honestly? relatable, she said it twice for emphasis 😭). this is the context that came in through async receive
  • sid β€” the address of the remote port you're sending the ABTS to πŸ“¬
  • xri β€” the oxid value for the ABTS, a.k.a. the other side's exchange id πŸ”₯

πŸ‘‘ SEE ALSO πŸ‘‘

first up, the kernel file this lives in, no cap:

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

and the friend group πŸ’– β€” all of these are (9) manual pages, go say hi:


ngl bestie, the whole squad is in ./drivers/scsi/lpfc and they all ate πŸ’… go read them all, iykyk

and that's the page!! πŸŽ€ cute little sign-off: this one comes from the source tree at ./drivers/scsi/lpfc, dated October 2026, and the page itself answers to lpfc_nvme_un..._issue_abort(9) 🌈 mwah, slay, bye πŸ’œ

πŸ“¦ where this page comes from