fc_lport_scr_resp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_lport_scr_resp(9) β€” like, the Kernel API Manual, bestie πŸ’…

okay so this is a page straight outta the Kernel API Manual, section 9, and it's all about handling the response to a State Change Register (SCR) request. FC girlies rise πŸ¦‹


✨ NAME ✨

fc_lport_scr_resp β€” handle the response to a State Change Register (SCR) request. that's it, that's the whole vibe πŸŽ€


🌸 SYNOPSIS 🌸

void fc_lport_scr_resp (struct fc_seq *sp , struct fc_frame *fp , void
*lp_arg );

🫢 ARGUMENTS 🫢

  • sp β€” the current sequence in the SCR exchange. lowkey the thread of the convo 🧡
  • fp β€” the response frame. the actual reply that came back, iconic ✨
  • lp_arg β€” the Fibre Channel lport port instance that sent the registration request. yes, the main character πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

Locking Note: this function gets called without the lport lock held β€” but no cap, it will lock, then call an _enter_* function or fc_lport_error, and then unlock the lport. so it's a whole lock β†’ do the thing β†’ unlock situation and it handles all of that for you πŸ’…

fr fr, read the locking note again. called unlocked, does its own locking, cleans up after itself. periodt.

πŸ’€ SEE ALSO πŸ’€

kernel file ./drivers/scsi/libfc/fc_lport.c and honestly the whole friend group:


mwah πŸ’œ this lil page lives in ./drivers/scsi/libfc and it's dated October 2026 β€” go off, future girlies. bye bestie, go lock something 🫢✨

πŸ“¦ where this page comes from