lpfc_sli4_l..._record_info(9)

🦋 lpfc_sli4_l..._record_info(9) — a whole page from the Kernel API Manual 🦋

Okay so bestie, this is the page for lpfc_sli4_l..._record_info(9), straight outta the Kernel API Manual, and it's literally the glow-up era for FCF logging. Buckle up, it's short but it ate. 💅

---

✨ NAME ✨

lpfc_sli4_log_fcf_record_info — logs the information of a fcf record. That's it, that's the whole job, and she does it so well. 🎀

---

🌸 SYNOPSIS 🌸

void lpfc_sli4_log_fcf_record_info (struct lpfc_hba *phba , struct
fcf_record *fcf_record , uint16_t vlan_id , uint16_t next_fcf_index );

No return value, no drama, just vibes and a void. Iconic. 💜

---

🫶 ARGUMENTS 🫶

• phba — pointer to lpfc hba data structure. The main character of the whole hba-verse, honestly. 👑
• fcf_record — pointer to the fcf record. Miss thing herself.
• vlan_id — the lowest vlan identifier associated to this fcf record. Lowestkey, but in a vlan way. 💀
• next_fcf_index — the index to the next fcf record in hba's fcf table. It's giving "linked list but make it fashion". ✨

---

🌈 DESCRIPTION 🌈

So this routine logs the detailed FCF record — but only if the LOG_FIP login is enabled. That's the vibe check, bestie: no LOG_FIP, no tea spilled. Enable it and you get the full detailed record; don't, and she simply does not. 🙈

---

💖 SEE ALSO 💖

Kernel file ./drivers/scsi/lpfc/lpfc_hbadisc.c — that's the home turf, iykyk. 🏠

And now the friend group, in the exact order they showed up to the party, fr fr:

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

That's fifty-one besties and every single one of them matters. Not me counting them all just to be sure. 😭💅

---

Bestie, that's the whole page — no bugs, no warnings, no exit statuses, just a clean little logger doing her thing. 🧚

And that's a wrap from ./drivers/scsi/lpfc, dated October 2026 — mwah, slay, periodt, go log something. 💖🔥👑