lpfc_issue_els_logo(9)

💅 lpfc_issue_els_logo — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, the file is ./drivers/scsi/lpfc/lpfc_els.c, and somebody needs to send a LOGO. this page is the whole lore. it lives in the Kernel API Manual, the header literally says lpfc_issue_els_logo(9), and we're about to break it all the way down 🎀

---

✨ NAME ✨

lpfc_issue_els_logo — Issue a logo to an node on a vport

(yes, "an node", we don't fix the kernel's grammar, we respect it 🫶)

---

🌸 SYNOPSIS 🌸

int lpfc_issue_els_logo (struct lpfc_vport *vport , struct lpfc_nodelist
*ndlp , uint8_t retry );

---

🦋 ARGUMENTS 🦋

• vport — pointer to a virtual N_Port data structure. that's your vport bestie 💜
• ndlp — pointer to a node-list data structure. the node in question 🎀
• retry — number of retries to the command IOCB. how many second chances the command IOCB gets 😭

---

🔥 DESCRIPTION 🔥

so what this routine actually does is construct and issue an ELS Logout (LOGO) iocb command to a remote node — and that remote node is referred to by an ndlp on a vport. it builds the payload of the IOCB, sets up the ndlp state properly (like, properly properly), and then invokes the lpfc_sli_issue_iocb routine to send out the LOGO ELS command. chef's kiss ✨

heads up, this part matters: the ndlp reference count will be incremented by 1 for holding the ndlp, and the reference to ndlp will be stored into the ndlp field of the IOCB — all so the completion callback function for the LOGO ELS command has something to work with. no cap 💅

and lowkey the most important bit: callers of this routine are expected to unregister the RPI first. like, before you call it. that's on you, not on this function 🙈

Return code:

• 0 — successfully issued logo 👑
• 1 — failed to issue logo 💀

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/scsi/lpfc/lpfc_els.c and, like, the entire extended universe of functions. all of them, we're not skipping a single one 🫡

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

---

🧚 the sign-off 🧚

and that's the whole page, periodt 💖 it came out of ./drivers/scsi/lpfc, dated October 2026, and the page itself is lpfc_issue_els_logo(9) from the Kernel API Manual — go unregister that RPI first, bestie, and slay 🌈👑✨