fc_timeout_fail_rport_io(9)
π« fc_timeout_fail_rport_io(9) π«
okay so bestie, welcome to fc_timeout_fail_rport_io(9) β yes that's the whole name, it's giving "my parents gave me a very long name and I'm owning it" energy and honestly? iconic. this is a Kernel API Manual page and we're gonna get through it together, no cap π«Ά
β¨ NAME β¨
fc_timeout_fail_rport_io β the timeout handler for a fast io that's failing on a disconnected SCSI target π
like, when things go wrong on a remote port that's already peaced out, this is the girl that gets called. periodt.
πΈ SYNOPSIS πΈ
void fc_timeout_fail_rport_io (struct work_struct *work );
literally that's it. one function, zero drama, takes a work struct pointer. copy it exactly, don't @ me π
π¦ ARGUMENTS π¦
workβ the rport to terminate io on π yep, that's what it says! it's a work struct but the doc says it's the rport to terminate io on, and we are NOT going to argue with the manual. it said what it said, bestie.
π₯ NOTES π₯
okay important, pay attention, this is the "read the group chat before replying" moment π
this only requests the failure of the io. it does not mean that all the io's have been flushed prior to returning. so like, don't come back asking "but is everything flushed??" because it literally just said it doesn't promise that. the request is made, the return happens, and that's the whole vibe check. π
no cap: the flush is NOT guaranteed here. do not assume it. this is not that kind of function.
π SEE ALSO π
alright buckle up because this list is LONG and we are listing every single one, no skipping, no summarising, because that would be rude to the whole entire kernel π
all of these live in the kernel file ./drivers/scsi/scsi_transport_fc.c π
fc_get_event_number(9)fc_host_post_fc_event(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_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)
thirty-one functions, bestie. THIRTY-ONE. and we listed every last one because that's what queens do πβ¨
and that's the page!! okay so this lil manpage came from the source tree at ./drivers/scsi, dated October 2026 bestie, and it's filed under the name fc_timeout_fail_rport_io(9) π mwah, go forth and fail those io requests responsibly π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms