lpfc_plogi_confirm_nport(9)

💅 lpfc_plogi_confirm_nport — Kernel API Manual, bestie edition ✨

💖 NAME 💖

lpfc_plogi_confirm_nport — confirm plogi wwpn matches stored ndlp 🫶

🌸 SYNOPSIS 🌸

okay so here’s the sacred signature, untouched, because code is literally code:

struct lpfc_nodelist * lpfc_plogi_confirm_nport (struct lpfc_hba *phba ,
uint32_t *prsp , struct lpfc_nodelist *ndlp );

🎀 ARGUMENTS 🎀

• phba — pointer to lpfc hba data structure. 💖
• prsp — pointer to response IOCB payload. ✨
• ndlp — pointer to a node-list data structure. 🦋

🦋 DESCRIPTION 🦋

okay so here’s the vibe: this routine checks and indicates whether the WWPN of an N_Port, retrieved from a PLOGI, matches the WWPN that is stored in the ndlp for that N_POrt. 👀

The following cases are considered N_Port confirmed:

• The N_Port is a Fabric ndlp. 🌸
• The ndlp is on the vport list and matches the WWPN of the N_Port logged into. 💅
• The ndlp is not on the vport list, but it does not have a WWPN assigned either. 🎀

If the WWPN is confirmed, the pointer to the ndlp will be returned. If the WWPN is not confirmed:

• If there is a node on the vport list other than the ndlp with the same WWPN of the N_Port PLOGI logged into, lpfc_unreg_rpi will be invoked on that node to release the RPI associated with the node. 🔥
• If there is no node found on the vport list with the same WWPN of the N_Port PLOGI logged into, a new node shall be allocated (or activated). ⭐

In either case, the parameters of the ndlp shall be copied to the new_ndlp, the ndlp shall be released, and the new_ndlp shall be put onto the vport node list and its pointer returned as the confirmed node. periodt. 👑

🚨 important plot twist, bestie: before the ndlp got "released", the keepDID from the not-matching or inactive new_ndlp on the vport node list is assigned to the nlp_DID of the ndlp. Why? Because the release of ndlp is actually to put it into an inactive state on the vport node list, and the vport node list management algorithm does not allow two nodes with the same DID. no cap. 💀

Return code: pointer to the PLOGI N_Port ndlp. 💖

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/lpfc/lpfc_els.c — yes, that’s the file, iykyk. The full squad, no skipping:

• lpfc_els_chk_latt(9), lpfc_prep_els_iocb(9), lpfc_issue_fabric_reglogin(9), lpfc_issue_reg_vfi(9), lpfc_issue_unreg_vfi(9), lpfc_check_clean_addr_bit(9), lpfc_cmpl_els_flogi_fabric(9)
• lpfc_cmpl_els_flogi_nport(9), lpfc_cmpl_els_flogi(9), lpfc_cmpl_els_link_down(9), lpfc_issue_els_flogi(9), lpfc_els_abort_flogi(9), lpfc_initial_flogi(9), lpfc_initial_fdisc(9)
• lpfc_more_plogi(9), lpfc_end_rscn(9), lpfc_cmpl_els_rrq(9), lpfc_check_encryption(9), lpfc_cmpl_els_plogi(9), lpfc_issue_els_plogi(9), lpfc_cmpl_els_prli(9)
• lpfc_issue_els_prli(9), lpfc_rscn_disc(9), lpfc_adisc_done(9), lpfc_more_adisc(9), lpfc_cmpl_els_adisc(9), lpfc_issue_els_adisc(9), lpfc_cmpl_els_logo(9)
• lpfc_issue_els_logo(9), lpfc_cmpl_els_cmd(9), lpfc_reg_fab_ctrl_node(9), lpfc_cmpl_els_disc_cmd(9), lpfc_issue_els_scr(9), lpfc_issue_els_rscn(9), lpfc_issue_els_farpr(9)
• lpfc_issue_els_rdf(9), lpfc_least_capable_settings(9), lpfc_cmpl_els_edc(9), lpfc_cancel_retry_delay_tmo(9), lpfc_els_retry_delay(9), lpfc_els_retry_delay_handler(9), lpfc_link_reset(9)
• lpfc_els_retry(9), lpfc_els_free_data(9), lpfc_els_free_bpl(9), lpfc_els_free_iocb(9), lpfc_cmpl_els_logo_acc(9), lpfc_mbx_cmpl_dflt_rpi(9), lpfc_cmpl_els_rsp(9)
• lpfc_els_rsp_acc(9), lpfc_els_rsp_reject(9), lpfc_els_rsp_adisc_acc(9), lpfc_els_rsp_prli_acc(9), lpfc_els_rsp_rnid_acc(9), lpfc_els_clear_rrq(9), lpfc_els_rsp_echo_acc(9)
• lpfc_els_disc_adisc(9), lpfc_els_disc_plogi(9), lpfc_els_rcv_lcb(9), lpfc_els_flush_rscn(9), lpfc_rscn_payload_check(9), lpfc_rscn_recovery_check(9), lpfc_send_rscn_event(9)
• lpfc_els_rcv_rscn(9), lpfc_els_handle_rscn(9), lpfc_els_rcv_flogi(9), lpfc_els_rcv_rnid(9), lpfc_els_rcv_echo(9), lpfc_els_rcv_lirr(9), lpfc_els_rcv_rrq(9)
• lpfc_els_rsp_rls_acc(9), lpfc_els_rcv_rls(9), lpfc_els_rcv_rtv(9), lpfc_send_rrq(9), lpfc_els_rsp_rpl_acc(9), lpfc_els_rcv_rpl(9), lpfc_els_rcv_farp(9)
• lpfc_els_rcv_farpr(9), lpfc_els_rcv_fan(9), lpfc_els_rcv_edc(9), lpfc_els_timeout(9), lpfc_els_timeout_handler(9), lpfc_els_flush_cmd(9), lpfc_els_flush_all_cmd(9)
• lpfc_send_els_failure_event(9), lpfc_send_els_event(9), lpfc_display_fpin_wwpn(9), lpfc_els_rcv_fpin_li(9), lpfc_els_rcv_fpin_del(9), lpfc_els_rcv_fpin_peer_cgn(9), lpfc_els_rcv_fpin_cgn(9)
• lpfc_els_unsol_buffer(9), lpfc_els_unsol_event(9), lpfc_do_scr_ns_plogi(9), lpfc_cmpl_reg_new_vport(9), lpfc_register_new_vport(9), lpfc_cancel_all_vport_retry_delay_timer(9), lpfc_retry_pport_discovery(9)
• lpfc_fabric_login_reqd(9), lpfc_cmpl_els_fdisc(9), lpfc_issue_els_fdisc(9), lpfc_cmpl_els_npiv_logo(9), lpfc_issue_els_npiv_logo(9), lpfc_fabric_block_timeout(9), lpfc_resume_fabric_iocbs(9)
• lpfc_unblock_fabric_iocbs(9), lpfc_block_fabric_iocbs(9), lpfc_cmpl_fabric_iocb(9), lpfc_issue_fabric_iocb(9), lpfc_fabric_abort_vport(9), lpfc_fabric_abort_nport(9), lpfc_fabric_abort_hba(9)
• lpfc_sli4_vport_delete_els_xri_aborted(9), lpfc_sli4_els_xri_aborted(9)

xoxo, from ./drivers/scsi/lpfc in October 2026 — this has been lpfc_plogi_confirm_nport(9) signing off 💅🫶✨