lpfc_nvme_fcp_abort(9)

📦 version 7.3.1, in nixpkgs unstable

Hiii bestie! Welcome to lpfc_nvme_fcp_abort(9) — a Kernel API Manual page, and it’s giving “NVMe-over-FCP abort handler” main character energy. We’re keeping every arg, every reference, and every little kernel detail, no cap. 💅✨

🎀 NAME 🎀

lpfc_nvme_fcp_abort — Issue an NVME-over-FCP ABTS.

✨ SYNOPSIS ✨

void lpfc_nvme_fcp_abort (struct nvme_fc_local_port *pnvme_lport ,
struct nvme_fc_remote_port *pnvme_rport , void *hw_queue_handle , struct
nvmefc_fcp_req *pnvme_fcreq );

🫶 ARGUMENTS 🫶

Okay bestie, here are the four things this function takes:

  • pnvme_lport — Pointer to the driver’s local port data. Local port data representation, slay.
  • pnvme_rport — Pointer to the rport getting the lpfc_nvme_ereq. Yes, exactly that.
  • hw_queue_handle — Driver-returned handle in lpfc_nvme_create_queue. Handle behavior, iconic.
  • pnvme_fcreq — IO request from nvme fc to driver. Request has entered the chat.

💖 DESCRIPTION 💖

Driver registers this routine as its nvme request io abort handler. This routine issues an fcp Abort WQE with data from the lpfc_nvme_fcpreq data structure to the rport indicated in lpfc_nvme_rport. This routine is executed asynchronously — once the target is validated as “MAPPED” and ready for IO, the driver issues the abort request and returns.

Return value: None.

Asynchronous behavior note, bestie: it doesn’t just sit there waiting around — the abort request goes out, and then it returns. 🦋

🔥 SEE ALSO 🔥

Kernel file first, because we stay organized: ./drivers/scsi/lpfc/lpfc_nvme.c. Then the whole friend group:

Okay bye bestie! 💖 This page’s source/version is ./drivers/scsi/lpfc, its date is October 2026, and the star of the show is still lpfc_nvme_fcp_abort(9). Slay, kernel manual, slay. 💅✨

📦 where this page comes from