lpfc_mbx_cm...read_fcf_rec(9)

💅 lpfc_mbx_cm...read_fcf_rec(9) 💅

okay so bestie, you opened the page for lpfc_mbx_cm...read_fcf_rec(9) from the Kernel API Manual, and it's giving “tiny kernel helper with main character energy.” Here's the whole thing, no cap, with every detail intact. 🫶

---

🌸 NAME 🌸

lpfc_mbx_cmpl_fcf_scan_read_fcf_rec — fcf scan read_fcf mbox cmpl handler. Literally that's the name, and yes, it's a mouthful. 💖

---

✨ SYNOPSIS ✨

void lpfc_mbx_cmpl_fcf_scan_read_fcf_rec (struct lpfc_hba *phba ,
       LPFC_MBOXQ_t *mboxq );

---

🎀 ARGUMENTS 🎀

• phba — pointer to lpfc hba data structure. That's the HBA's data, bestie.
• mboxq — pointer to mailbox object. The mailbox object in question. 💌

---

🦋 DESCRIPTION 🦋

okay so here's the vibe: this function iterates through all the fcf records available in HBA and chooses the optimal FCF record for discovery. After finding the FCF for discovery it registers the FCF record and kicks start discovery. ✨

If FCF_IN_USE flag is set in currently used FCF, the routine tries to use an FCF record which matches fabric name and mac address of the currently used FCF record. It's lowkey doing a matching quest. 💅

If the driver supports only one FCF, it will try to use the FCF record used by BOOT_BIOS. Periodt. 🔥

---

👑 SEE ALSO 👑

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

The whole friend group:

• lpfc_check_inactive_vmid_one(9)
• lpfc_check_inactive_vmid(9)
• lpfc_check_nlp_post_devloss(9)
• lpfc_dev_loss_tmo_handler(9)
• lpfc_sli4_post_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_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)

---

source/version: ./drivers/scsi/lpfc · date: October 2026 · page: lpfc_mbx_cm...read_fcf_rec(9) — okay bestie, that's the whole tea, go slay your FCF discovery 💅✨🦋