fc_disc_recv_req(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ fc_disc_recv_req(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this one's a little cutie from the depths of the SCSI libfc code, and honestly? she's short but she matters. let's get into it 🫢


🌸 NAME 🌸

fc_disc_recv_req β€” handle incoming requests ✨ (yes that's it, that's her whole job, and she does it gorgeously)


πŸ¦‹ SYNOPSIS πŸ¦‹

void fc_disc_recv_req (struct fc_lport *lport , struct fc_frame *fp );

like... look at that signature. no return value, just vibes and business πŸ’€ she takes two things and gives you nothing back except handled requests.


πŸŽ€ ARGUMENTS πŸŽ€

  • lport β€” the local port that's receiving the request πŸ‘‘ this is the main character of the operation, the port doing the actual receiving, ngl
  • fp β€” the request frame 🌈 literally the frame carrying the request, that's the whole vibe

πŸ’– DESCRIPTION πŸ’–

so here's the tea, bestie β˜• β€”

Locking Note: this function gets called from the EM, and it will lock disc_mutex before it calls the handler for the request πŸ”’βœ¨ like, it's not out here raw-dogging the handler with no lock, okay? it locks first, then calls. periodt.

heads up: that locking note is the entire described behaviour here β€” don't go inventing extra steps in your head, this is a "lock the mutex, call the handler" girlie and nothing more πŸ’…

🧚 SEE ALSO 🧚

the whole discovery squad shows up here, and they're all iconic in their own way πŸ˜­πŸ’œ

Kernel file ./drivers/scsi/libfc/fc_disc.c 🌸 and the besties:

like, the way that list just keeps going?? she's connected, she knows everyone, main character energy fr fr πŸ‘‘


and that's the page!! πŸ¦‹ this icon lives over at ./drivers/scsi/libfc, dated October 2026, and you can find her under the name fc_disc_recv_req(9) whenever you need her πŸ’–βœ¨ slay, go handle those requests bestie πŸŽ€

πŸ“¦ where this page comes from