fc_disc_gpn_id_resp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fc_disc_gpn_id_resp(9) — like, the Kernel API Manual page, bestie

okay so welcome to the Kernel API Manual ✨ and today's main character is fc_disc_gpn_id_resp(9). yes, that's a function. yes, section 9. yes, it's giving kernel-internals realness 🎀

✨ NAME ✨

fc_disc_gpn_id_resp — handles a response frame from Get Port Names (GPN_ID) 🦋

like literally that's her whole job. she takes the response frame from GPN_ID and deals with it. no cap.

🌸 SYNOPSIS 🌸

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

so she's a void function (nothing comes back out, she just does the thing 💅) and she takes three args — sp, fp, and rdata_arg. keep the exact signature, bestie, this is not the place to freestyle 🙈

🫶 ARGUMENTS 🫶

  • sp — the sequence that the GPN_ID is on ⭐ like, which sequence we're talking about, this is it
  • fp — the response frame 💌 the actual frame that came back, right here
  • rdata_arg — the remote port that sent the GPN_ID response 👑 the remote port responsible, that's her

💜 DESCRIPTION 💜

Locking Note: this function is called without the disc mutex held. 🔥

that's the whole description, and honestly? it's the important part. the disc mutex is not held when you call this — so don't go assuming it's chillin' in there, because she is not 😭

🦋 SEE ALSO 🦋

Kernel file ./drivers/scsi/libfc/fc_disc.c — plus the whole friend group, and yes we're listing every single one because nobody gets left out of the group chat 💖

and that's the page, bestie! 🌈 sign-off time: this one lives in ./drivers/scsi/libfc, it's from October 2026, and it's part of the Kernel API Manual — fc_disc_gpn_id_resp(9), periodt 💅✨

📦 where this page comes from