nvmet_fc_rcv_fcp_abort(9)

💅 nvmet_fc_rcv_fcp_abort(9) 💅

okay so bestie, this is a page from the Kernel API Manual and it's literally about nvmet_fc_rcv_fcp_abort — the transport entry point your LLDD calls when an ABTS shows up for an FCP command. yes we're starting with the plot twist, keep up 🎀

---

✨ NAME ✨

nvmet_fc_rcv_fcp_abort — the transport entry point that gets called by an LLDD when an ABTS arrives for an FCP command 🦋

---

🌸 SYNOPSIS 🌸

void nvmet_fc_rcv_fcp_abort (struct nvmet_fc_target_port *target_port ,
struct nvmefc_tgt_fcp_req *fcpreq );

---

🎀 ARGUMENTS 🎀

• target_port — pointer to the (registered) target port that the FCP CMD IU was received on. it's the port, it's registered, it's giving main character energy 👑
• fcpreq — pointer to the fcpreq request structure that corresponds to the exchange which received the ABTS. like, that exchange 🫶

---

🔥 DESCRIPTION 🔥

So what this does is notify the transport that an ABTS has been received for a FCP command that had been given to the transport via nvmet_fc_rcv_fcp_req. and where's the LLDD in all this? the LLDD believes the command is still being worked on — meaning template_ops->fcp_req_release has not been called. ngl, that's the whole vibe check here 💀

The transport will wait for any outstanding work — that's either an op to the LLDD, which the LLDD should complete with error due to the ABTS, or the completion from the nvmet layer of the nvme command. then, after all that, it will stop processing and call the nvmet_fc_rcv_fcp_req callback to return the i/o context to the LLDD. slay 💅

And the LLDD? it may send the BA_ACC to the ABTS either after return from this function — assuming any outstanding op work has been terminated — or upon the callback being called. two valid paths, both iconic ✨

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/nvme/target/fc.c
• nvmet_fc_register_targetport(9)
• nvmet_fc_invalidate_host(9)
• nvmet_fc_unregister_targetport(9)
• nvmet_fc_rcv_ls_req(9)
• nvmet_fc_rcv_fcp_req(9)

go read the whole friend group, fr fr 📚

---

and that's the page bestie!! 🍓 coming at you from ./drivers/nvme/target, dated October 2026 — no cap, that's the source and the date, go off calendar icon you ate 💖✨🧚