fcoe_ctlr_vn_probe_reply(9)

📦 version 7.3.1, in nixpkgs unstable

💖 fcoe_ctlr_vn_probe_reply — kernel API manual, bestie edition 💖

Okay so this one's from the Kernel API Manual, and it's literally about handling an incoming VN2VN probe reply. It's short, it's sweet, and it's giving "tiny function, big responsibility" energy. Let's get into it 🎀

✨ NAME ✨

fcoe_ctlr_vn_probe_reply — handles an incoming VN2VN probe reply. That's it, that's the whole gig 🦋

🌸 SYNOPSIS 🌸

void fcoe_ctlr_vn_probe_reply (struct fcoe_ctlr *fip , struct fcoe_rport
*frport );

Look at that return type: void. She doesn't return anything, she just does things. Main character energy fr fr 👑

💜 ARGUMENTS 💜

  • fip — the FCoE controller 🫶 this is your controller bestie, the one holding it all together.
  • frport — the parsed FCoE rport from the probe request. Yep, from the probe request — that's what the original says, don't come for me 💅

🌈 DESCRIPTION 🌈

Called with ctlr_mutex held. That's the entire description, bestie, I'm not even kidding 😭

So like, the one thing you absolutely cannot miss: ctlr_mutex is held when this runs. That's the vibe check this function lives by. No cap, that's the whole note 📝

🔥 SEE ALSO 🔥

We got a whole friend group here, and honestly? Obsessed with how many of them there are. All of these live in the kernel file ./drivers/scsi/fcoe/fcoe_ctlr.c:

Like, that's a lot of see-also's. She knows everyone at the party 🎉 And yeah, the file lives under ./drivers/scsi/fcoe — that's the ./drivers/scsi/fcoe directory, bestie, don't lose her 💀

Go read the related ones if you're curious about VN2VN probing — the probe request twin is right there in the list: fcoe_ctlr_vn_probe_req(9) 🧚

That's the whole page! ✨ Written out of the ./drivers/scsi/fcoe corner of the kernel tree, from the October 2026 vintage of this here Kernel API Manual, starring fcoe_ctlr_vn_probe_reply(9). Mwah, love u, go hold your ctlr_mutex responsibly 💜🎀

📦 where this page comes from