fc_fcp_recv(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fc_fcp_recv — the group chat version

okay so bestie, quick vibe check: this page lives in the Kernel API Manual, and it's all about one little function that just… receives an FCP frame. that's it. that's the whole personality. and honestly? iconic that something so small gets its own manpage. no cap. 🎀

✨ NAME ✨

fc_fcp_recv — receive an FCP frame 💌

like, a frame literally arrives, and this is the function that's there to catch it. main character energy fr fr.

🦋 SYNOPSIS 🦋

void fc_fcp_recv (struct fc_seq *seq , struct fc_frame *fp , void *arg
);

yes it returns void. yes it's three arguments. yes the trailing ); is on its own line and we are not touching it, that's just how it's written, periodt. 💅

🌸 ARGUMENTS 🌸

  • seq — the sequence that the frame is riding on. think of it as the frame's lil context, its "which conversation am I in" energy. 💬
  • fp — the actual received frame. the star of the show, the package, the whole reason we're here. 📦
  • arg — the related FCP packet. the buddy that comes along with the frame, iykyk. 🫶

🔥 CONTEXT 🔥

okay this part matters, so pay attention bestie 👀:

this gets called from Soft IRQ context. so like, interrupt-adjacent land. not sleepy regular-process energy.

and — the big one — it can not be called while holding the FCP packet list lock. like, do not do that. that's a hard nope. the manpage says so, I'm just relaying the message. 🙈

lowkey important: no holding the FCP packet list lock. not even a little. not even if you're being cute about it. 🚫🔒

🌈 SEE ALSO 🌈

okay this list is long and every single one of these is here, so buckle up bestie, we're going through the whole squad 👑

like I said. the whole squad. go read them if you're curious, they're all in ./drivers/scsi/libfc and they all ate. 🍓

and that's the page, bestie!! 💖 this lil rewrite comes to you courtesy of ./drivers/scsi/libfc, dated October 2026 — go off, you gorgeous kernel file, you. 🧚‍♀️⭐👑

📦 where this page comes from