lpfc_sli4_p..._tmo_handler(9)

💖 NAME 💖

lpfc_sli4_post_dev_loss_tmo_handler — SLI4 post devloss timeout handler.

okay bestie, welcome to lpfc_sli4_p..._tmo_handler(9) — this is the Kernel API Manual page for lpfc_sli4_post_dev_loss_tmo_handler, and we're gonna get you comfy with it. 💖

---

✨ SYNOPSIS ✨

here's the exact signature, no cap:

void lpfc_sli4_post_dev_loss_tmo_handler (struct lpfc_hba *phba , int
fcf_inuse , uint32_t nlp_did );

---

🎀 ARGUMENTS 🎀

three args, three vibes:

• phba — pointer to the hba context object.
• fcf_inuse — the SLI4 FCF in-use state reported from the devloss timeout handler.
• nlp_did — remote node identifer with devloss timeout.

---

🦋 DESCRIPTION 🦋

okay so picture this: this function gets called from the worker thread after the devloss timeout handler has been invoked and after the reference count has been released for the ndlp with which the devloss timeout was handled, for an SLI4 host. That's the setup.

For the devloss timeout of the last remote node which had been in use of the FCF, when this routine is invoked, it shall be guaranteed that none of the remote are in-use of the FCF. 🫶

When the devloss timeout is to the last remote using the FCF: if the FIP engine is neither in the FCF table scan process nor in the roundrobin failover process, the in-use FCF shall be unregistered. periodt.

If the FIP engine is in the FCF discovery process, then the devloss timeout state shall be set for either the FCF table scan process or the roundrobin failover process, to unregister the in-use FCF. iykyk.

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/scsi/lpfc/lpfc_hbadisc.c

and the whole related-call squad:

• lpfc_check_inactive_vmid_one(9)
• lpfc_check_inactive_vmid(9)
• lpfc_check_nlp_post_devloss(9)
• lpfc_dev_loss_tmo_handler(9)
• lpfc_alloc_fast_evt(9)
• lpfc_free_fast_evt(9)
• lpfc_send_fastpath_evt(9)
• lpfc_sli4_clear_fcf_rr_bmask(9)
• lpfc_fab_name_match(9)
• lpfc_sw_name_match(9)
• lpfc_mac_addr_match(9)
• __lpfc_update_fcf_record_pri(9)
• lpfc_copy_fcf_record(9)
• __lpfc_update_fcf_record(9)
• lpfc_register_fcf(9)
• lpfc_match_fcf_conn_list(9)
• lpfc_check_pending_fcoe_event(9)
• lpfc_sli4_new_fcf_random_select(9)
• lpfc_sli4_fcf_rec_mbox_parse(9)
• lpfc_sli4_log_fcf_record_info(9)
• lpfc_sli4_fcf_record_match(9)
• lpfc_sli4_fcf_rr_next_proc(9)
• lpfc_sli4_fcf_pri_list_del(9)
• lpfc_sli4_set_fcf_flogi_fail(9)
• lpfc_sli4_fcf_pri_list_add(9)
• lpfc_mbx_cmpl_fcf_scan_read_fcf_rec(9)
• lpfc_mbx_cmpl_fcf_rr_read_fcf_rec(9)
• lpfc_mbx_cmpl_read_fcf_rec(9)
• lpfc_init_vfi_cmpl(9)
• lpfc_issue_init_vfi(9)
• lpfc_init_vpi_cmpl(9)
• lpfc_issue_init_vpi(9)
• lpfc_start_fdiscs(9)
• lpfc_create_static_vport(9)
• lpfc_issue_gidpt(9)
• lpfc_initialize_node(9)
• lpfc_nlp_logo_unreg(9)
• lpfc_unreg_hba_rpis(9)
• lpfc_find_vport_by_vpid(9)
• lpfc_fcf_inuse(9)
• lpfc_unregister_vfi_cmpl(9)
• lpfc_unregister_fcfi_cmpl(9)
• lpfc_unregister_fcf_prep(9)
• lpfc_sli4_unregister_fcf(9)
• lpfc_unregister_fcf_rescan(9)
• lpfc_unregister_fcf(9)
• lpfc_unregister_unused_fcf(9)
• lpfc_read_fcf_conn_tbl(9)
• lpfc_read_fcoe_param(9)
• lpfc_get_rec_conf23(9)
• lpfc_parse_fcoe_conf(9)

---

okay that's the whole page, bestie! it's sourced from ./drivers/scsi/lpfc, dated October 2026, and it's the lpfc_sli4_p..._tmo_handler(9) page — mwah 💋✨