fc_rport_prli_resp(9)

🌸 fc_rport_prli_resp (9) — the Kernel API Manual, but make it a group chat 🌸

okay so bestie, this page is from the Kernel API Manual, section 9, and it's all about the function fc_rport_prli_resp — yeah, say that five times fast 💅 don't worry, we'll get through it together.

---

✨ NAME ✨

fc_rport_prli_resp — the Process Login (PRLI) response handler 🎀

Like, when a PRLI response shows up, this is the girl who answers the door. main character energy fr.

---

🦋 SYNOPSIS 🦋

void fc_rport_prli_resp (struct fc_seq *sp , struct fc_frame *fp , void
*data_arg );

ngl bestie, keep that signature exactly as it is — copy-paste is your friend here 🙈

---

🍓 ARGUMENTS 🍓

• sp — the sequence the PRLI response was on. that's her ride, her context, her whole situation ✨
• fp — the PRLI response frame itself. the actual message, the moment, the drama 💌
• rdata_arg — the remote port that sent the PRLI response. the sender, the one who slid into the frame 😭

---

💜 DESCRIPTION 💜

Locking Note: okay this is the important part, so listen up 🫶 — this function will be called without the rport lock held. but then it will lock, call an _enter_* function or fc_rport_error, and then unlock the rport.

so yeah: no lock coming in, locks it herself, does the thing, unlocks, done. iconic, self-sufficient, no cap 👑

---

🌈 SEE ALSO 🌈

and now for the whole squad — the Kernel file ./drivers/scsi/libfc/fc_rport.c is the home base, and these are literally all the friends:

• fc_rport_lookup (9)
• fc_rport_create (9)
• fc_rport_destroy (9)
• fc_rport_state (9)
• fc_set_rport_loss_tmo (9)
• fc_plogi_get_maxframe (9)
• fc_rport_state_enter (9)
• fc_rport_work (9)
• fc_rport_login (9)
• fc_rport_enter_delete (9)
• fc_rport_logoff (9)
• fc_rport_enter_ready (9)
• fc_rport_timeout (9)
• fc_rport_error (9)
• fc_rport_error_retry (9)
• fc_rport_login_complete (9)
• fc_rport_flogi_resp (9)
• fc_rport_enter_flogi (9)
• fc_rport_recv_flogi_req (9)
• fc_rport_plogi_resp (9)
• fc_rport_enter_plogi (9)
• fc_rport_enter_prli (9)
• fc_rport_rtv_resp (9)
• fc_rport_enter_rtv (9)
• fc_rport_recv_rtv_req (9)
• fc_rport_logo_resp (9)
• fc_rport_enter_logo (9)
• fc_rport_adisc_resp (9)
• fc_rport_enter_adisc (9)
• fc_rport_recv_adisc_req (9)
• fc_rport_recv_rls_req (9)
• fc_rport_recv_els_req (9)
• fc_rport_recv_req (9)
• fc_rport_recv_plogi_req (9)
• fc_rport_recv_prli_req (9)
• fc_rport_recv_prlo_req (9)
• fc_rport_recv_logo_req (9)
• fc_rport_flush_queue (9)
• fc_rport_fcp_prli (9)
• fc_rport_t0_prli (9)
• fc_setup_rport (9)
• fc_destroy_rport (9)
• fc_rport_terminate_io (9)

like, the entire friend group showed up to the function's birthday party 🎉 and honestly? we love that for them.

---

that's the whole page, bestie — go forth and handle those PRLI responses 💖

this one came from ./drivers/scsi/libfc and it's dated October 2026 — so yeah, timestamps say that, and I'm just the messenger 🫡✨