fc_host_post_vendor_event(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fc_host_post_vendor_event — from the Kernel API Manual, bestie ✨

okay so picture this: it's giving kernel API, it's giving Fibre Channel, and the manual it lives in is literally called the Kernel API Manual. this is the function you call when you gotta post a vendor unique event on an fc_host. iconic behavior only 🦋

🌸 NAME 🌸

fc_host_post_vendor_event — the one you call to post a vendor unique event on an fc_host. that's it, that's the whole vibe 🎀

✨ SYNOPSIS ✨

void fc_host_post_vendor_event (struct Scsi_Host *shost , u32
event_number , u32 data_len , char * data_buf , u64 vendor_id );

like, it returns void, so don't go looking for a return value, there isn't one, periodt 💀

🫶 ARGUMENTS 🫶

  • shost — the host the event occurred on. this is the main character right here 👑
  • event_number — the fc event number, which you get from get_fc_event_number. don't just make one up, go get it 💅
  • data_len — the amount, in bytes, of vendor unique data. yes, bytes, keep up 🍓
  • data_buf — pointer to the vendor unique data. it's a char *, she's pointing at your stuff 🧚
  • vendor_id — the Vendor id. that's it, that's the description, no notes 🌈

🔥 NOTES 🔥

this routine assumes no locks are held on entry. so like, if you're holding a lock when you call this, that's not the move, bestie — check yourself before you wreck yourself 🙈

⭐ SEE ALSO ⭐

the kernel file ./drivers/scsi/scsi_transport_fc.c is where all the lore lives, and it's linked to all of these besties — every single one, no skips, we don't do that here 💖

reading list for the girlies: all 33 of these, in order, with snacks. iykyk 🍓

and that's a wrap! this page lives in ./drivers/scsi, it's dated October 2026, and it's filed under fc_host_post_vendor_event(9). slay, go post some vendor unique events responsibly 💜✨🎀

📦 where this page comes from