lpfc_nvmet_u...cp_abort_cmp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the Kernel API Manual πŸ’– β€” this page is all about lpfc_nvmet_unsol_fcp_abort_cmp, and the header up top is doing its little truncated lpfc_nvmet_u...cp_abort_cmp(9) moment. We’re folding that manual-name vibe in right here, no cap.

🌸 NAME 🌸

lpfc_nvmet_unsol_fcp_abort_cmp β€” Completion handler for ABTS. That’s her. That’s the whole name, periodt ✨.

✨ SYNOPSIS ✨

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

That’s the signature, fr fr β€” three pointers and main character energy 🫢.

πŸ’… ARGUMENTS πŸ’…

The way this signature is giving three lil pointer besties, and every single one matters:

  • phba β€” Pointer to HBA context object.
  • cmdwqe β€” Pointer to driver command WQE object.
  • rspwqe β€” Pointer to driver response WQE object.

πŸŽ€ DESCRIPTION πŸŽ€

Okay so picture this: the function is called from the SLI ring event handler with no lock held β€” literally, bestie, no lock. She is the completion handler for NVME ABTS for FCP cmds, and the way she does her job is by freeing the memory resources used for the NVME commands. That’s the whole plot, and she ate πŸ’….

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/scsi/lpfc/lpfc_nvmet.c 🌈

The whole friend group is here, and yes every single reference is invited:


xoxo bestie πŸ«ΆπŸ’– β€” the source/version bit is ./drivers/scsi/lpfc, the date is October 2026, and the page tag is lpfc_nvmet_u...cp_abort_cmp(9). Mwah! πŸŽ€βœ¨

πŸ“¦ where this page comes from