lpfc_match_fcf_conn_list(9)

💅 lpfc_match_fcf_conn_list(9) — Kernel API Manual ✨

okay so bestie, we're in the kernel API manual and today's main character is lpfc_match_fcf_conn_list — the little function that does a whole vibe check on your FCF record before letting it into the club 🎀

---

🌸 NAME 🌸

lpfc_match_fcf_conn_list — checks whether an FCF record is actually allowed to be used for discovery 👀

---

⭐ SYNOPSIS ⭐

int lpfc_match_fcf_conn_list (struct lpfc_hba *phba , struct fcf_record
*new_fcf_record , uint32_t *boot_flag , uint32_t *addr_mode , uint16_t
*vlan_id );

---

🦋 ARGUMENTS 🦋

• phba — pointer to the lpfc hba data structure, the main character of the whole operation 💖
• new_fcf_record — pointer to the fcf record, aka the thing we're judging 🔍
• boot_flag — tells you whether this record is used by boot bios
• addr_mode — the address mode this FCF is gonna use
• vlan_id — the vlan id that gets used as vlan tagging by this FCF

---

💜 DESCRIPTION 💜

so what this routine does is compare the fcf record against the connect list it grabbed from the config region, and from that it decides whether this FCF can serve SAN discovery 🫶

the return value is literally iconic in its simplicity: it returns 1 if this record can be used for SAN discovery, and returns zero otherwise. no in-between, no "it's complicated" 💅

and if this FCF record can be used for SAN discovery, then two of your out-params light up on return:

• boot_flag will indicate whether this FCF is used by boot bios
• addr_mode will indicate the addressing mode to be used for this FCF

also — if the FCF record needs to be used with a particular vlan id, that vlan gets set in vlan_id when the function returns ✨

and if no VLAN tagging needs to be used with the FCF, then vlan_id gets set to LPFC_FCOE_NULL_VID. periodt 🎀

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/lpfc/lpfc_hbadisc.c — go read the source bestie, it's all there 📖

• 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_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)

---

ngl that SEE ALSO list is serving major "linked list of destiny" energy — click through them at your own pace, no pressure 🧚

---

and that's the whole page!! drop a 🫶 for the ./drivers/scsi/lpfc crew — this one's dated October 2026 and it's filed under lpfc_match_fcf_conn_list(9). slay, go match some FCFs bestie 🎀✨💅