lpfc_get_rec_conf23(9)
π lpfc_get_rec_conf23 β a kernel API manual (yes the whole manual name is in the title, we're doing this) β¨
okay so bestie, sit down, hydrate, because today we're reading a kernel API manual page and honestly? it's kinda iconic. it's called lpfc_get_rec_conf23, and no I will not be pronouncing that out loud. π
πΈ NAME πΈ
lpfc_get_rec_conf23 β get a record type in config region data. that's it. that's the whole job. she's a finder. a little search gremlin. π§
β¨ SYNOPSIS β¨
uint8_t * lpfc_get_rec_conf23 (uint8_t *buff , uint32_t size , uint8_t
rec_type );
three args, one pointer back, no drama. copy it exactly, babes, the kernel does not accept vibes-based syntax. π
π¦ ARGUMENTS π¦
buffβ the buffer holding config region 23 data. like, the actual data. the stuff. πsizeβ how big that data buffer is. you gotta tell her, she's not a mind reader.rec_typeβ the record type you want her to go hunt for. the target. the main character of this search. π
π DESCRIPTION π
so what she does is: she searches through config region data to find the beginning of the record specified by record_type. That's the whole personality.
if the record is found β she returns a pointer to that record. found it, slayed, periodt. β¨
if it's not found β she returns NULL. no record, no pointer, no notes. π
ngl the "return" vs "returns" grammar in the original is a whole mood but the meaning is locked in: found = pointer, not found = NULL. no in-between, no maybe, no "it's complicated". π
π SEE ALSO π
first up, the kernel file where this lives:
./drivers/scsi/lpfc/lpfc_hbadisc.c
and then... the friend group. the entire extended cinematic universe. all of these, in this order, no skips: π
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_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_parse_fcoe_conf(9)
like I said. the whole friend group. read them, they're all linked, iykyk. π«Ά
okay that's the page!! this little cutie comes from the source path ./drivers/scsi/lpfc and the version/date line says October 2026, header name lpfc_get_rec_conf23(9), so yeah β she's from the future, she's in ./drivers/scsi/lpfc, and she's gotta go. mwah. ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms