fc_host_post_fc_event(9)

💖 fc_host_post_fc_event(9) 💖

Okay so welcome to the Kernel API Manual, bestie! The main character today is fc_host_post_fc_event — literally the routine to do the work of posting an event on an fc_host. She ate and left no crumbs. 💅✨

🎀 NAME 🎀

fc_host_post_fc_event — routine to do the work of posting an event on an fc_host. Periodt. 💅

✨ SYNOPSIS ✨

The signature is exactly this, no edits, no cap:

void fc_host_post_fc_event (struct Scsi_Host *shost , u32 event_number , enum fc_host_event_code event_code , u32 data_len , char *data_buf , u64 vendor_id );

🦋 ARGUMENTS 🦋

• shost — host the event occurred on. 🏠
• event_number — fc event number obtained from get_fc_event_number. 🔢
• event_code — fc_host event being posted. 📮
• data_len — amount, in bytes, of event data. 📏
• data_buf — pointer to event data. 📦
• vendor_id — value for Vendor id. 🏷️

💀 NOTES 💀

Important vibe check: this routine assumes no locks are held on entry. That's the whole note, bestie. 🔒

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/scsi_transport_fc.c — and the whole squad is here, no skips:

• fc_get_event_number(9)
• fc_host_post_event(9)
• fc_host_post_vendor_event(9)
• fc_find_rport_by_wwpn(9)
• fc_host_fpin_rcv(9)
• fc_eh_timed_out(9)
• fc_queue_work(9)
• fc_flush_work(9)
• fc_queue_devloss_work(9)
• fc_flush_devloss(9)
• fc_remove_host(9)
• fc_starget_delete(9)
• fc_rport_final_delete(9)
• fc_remote_port_create(9)
• fc_remote_port_add(9)
• fc_remote_port_delete(9)
• fc_remote_port_rolechg(9)
• fc_timeout_deleted_rport(9)
• fc_timeout_fail_rport_io(9)
• fc_scsi_scan_rport(9)
• fc_block_rport(9)
• fc_block_scsi_eh(9)
• fc_vport_setup(9)
• fc_vport_create(9)
• fc_vport_terminate(9)
• fc_vport_sched_delete(9)
• fc_bsg_job_timeout(9)
• fc_bsg_host_dispatch(9)
• fc_bsg_rport_dispatch(9)
• fc_bsg_hostadd(9)
• fc_bsg_rportadd(9)
• fc_bsg_remove(9)

Catch ya later, bestie! This page's source/version stamp is ./drivers/scsi, dated October 2026, and it's the fc_host_post_fc_event(9) manual page. 💜🫶🎀