fc_rport_plogi_resp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fc_rport_plogi_resp — a Kernel API Manual moment

okay so bestie, welcome to fc_rport_plogi_resp(9) 🎀 this one lives in the Kernel API Manual and she is, and I cannot stress this enough, the handler for ELS PLOGI responses. no cap. let's get into it ✨

🌸 SYNOPSIS 🌸

void fc_rport_plogi_resp (struct fc_seq *sp , struct fc_frame *fp , void
*rdata_arg );

like literally that's the whole vibe. void, three args, no return value, she simply does her job and leaves 🫶

💖 ARGUMENTS 💖

  • sp — the sequence the PLOGI is on. this is the where, the main character context, the sequence energy ✨
  • fp — the PLOGI response frame itself. the actual payload coming through, the moment we've all been waiting for 💌
  • rdata_arg — the remote port that sent the PLOGI response. hi bestie 👋 yes you, the sender

🔥 DESCRIPTION 🔥

okay so the big thing here, and I need you to actually read this part:

Locking Note: this function will be called without the rport lock held — not with it, without it 💀 but then she locks, calls an _enter_* function or fc_rport_error, and then unlocks the rport. so like… it locks, does the thing, unlocks. a whole little lock-unlock sandwich. iconic behavior, honestly. no cap, that's the entire dance 🩰

👑 SEE ALSO 👑

the entire friend group, fr fr, all of them (9), and yes I listed every single one because I would never do my girls dirty 💜 also they all live in the kernel file ./drivers/scsi/libfc/fc_rport.c:

okay that's the whole page bestie, go touch some frames 💅✨

from ./drivers/scsi/libfc, dated October 2026 — mwah, kisses, that's the sign-off 🎀🦋💜

📦 where this page comes from