__lpfc_updat...f_record_pri(9)

💅 __lpfc_updat...f_record_pri(9) — from the Kernel API Manual, bestie ✨

okay so picture this: you're deep in the kernel, SCSCI lpfc land, and there's this one little function that just wants to keep your FCF priority record cute and up to date. she's not flashy, she's just doing her job 🎀 and honestly? iconic behavior.

---

🌸 NAME 🌸

__lpfc_update_fcf_record_pri — literally just updates the lpfc_fcf_pri record. that's the whole vibe. no cap 💅

---

🦋 SYNOPSIS 🦋

void __lpfc_update_fcf_record_pri (struct lpfc_hba *phba , uint16_t
fcf_index , struct fcf_record *new_fcf_record );

look at her go. returns void, takes three args, zero drama ✨

---

💖 ARGUMENTS 💖

• phba — pointer to the lpfc hba data structure. yes queen, this is the main character 🫶
• fcf_index — the index for the lpfc_fcf_record. like her little address in the group chat, iykyk
• new_fcf_record — pointer to the hba fcf record. this is the fresh new tea that's getting copied over ☕

---

⭐ DESCRIPTION ⭐

so here's what's happening: this routine updates the driver's FCF priority record using the new HBA FCF record. she's a copy-paste girly, but make it kernel-grade 💅

also — important — the hbalock is asserted held in the code path that calls this routine. so do NOT come in here un-locked, that's not the move 😭 lock it first, periodt.

🔥 real talk: this isn't a "call me whenever" function. the caller has already grabbed hbalock and is holding it. respect the lock, bestie.

---

🌈 SEE ALSO 🌈

she runs in ./drivers/scsi/lpfc/lpfc_hbadisc.c — go say hi to the whole family 💜

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

like. fifty functions. one friend group. we love a connected community 🧚💜

---

okay that's the whole page, you ate that 🫶 giving you a lil sign-off: this one lives in ./drivers/scsi/lpfc and it's dated October 2026, and the page itself is __lpfc_updat...f_record_pri(9) — yes the title is truncated, no that's not a typo, that's just how she's filed 💅✨