lpfc_bsg_diag_loopback_mode(9)
π lpfc_bsg_diag_loopback_mode(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β yes, the actual Linux kernel API manual, and yes, we're gonna get through this together. This one's about lpfc_bsg_diag_loopback_mode, which is a bsg vendor command for diag loopback mode π. That's it, that's the whole vibe. Let's go π¦
β¨ SYNOPSIS β¨
int lpfc_bsg_diag_loopback_mode (struct bsg_job *job );
literally that's the whole signature, no cap. returns an int, takes one thing. slay π
π«Ά ARGUMENTS π«Ά
jobβ this is theLPFC_BSG_VENDOR_DIAG_MODEone π. like, that's the argument, that's what it is. periodt.
πΈ DESCRIPTION πΈ
so what does this icon actually do? π§
this function is responsible for responding to check and dispatch bsg diag command from the user to proper driver action routines β¨.
read that again, it's giving traffic controller energy fr fr β a diag command comes in from the user, this thing checks it and dispatches it to the right driver action routine. main character behavior honestly ππ
π₯ SEE ALSO π₯
okay this list is LONG, bestie, buckle up, we're going through all of them because every single one matters π
the kernel file:
./drivers/scsi/lpfc/lpfc_bsg.c
and now the friends of the family, in order, all of them, no skipping π:
lpfc_bsg_send_mgmt_cmd_cmp(9)lpfc_bsg_send_mgmt_cmd(9)lpfc_bsg_rport_els_cmp(9)lpfc_bsg_rport_els(9)lpfc_bsg_event_free(9)lpfc_bsg_event_ref(9)lpfc_bsg_event_unref(9)lpfc_bsg_event_new(9)diag_cmd_data_free(9)lpfc_bsg_ct_unsol_abort(9)lpfc_bsg_hba_set_event(9)lpfc_bsg_hba_get_event(9)lpfc_issue_ct_rsp_cmp(9)lpfc_issue_ct_rsp(9)lpfc_bsg_send_mgmt_rsp(9)lpfc_bsg_diag_mode_enter(9)lpfc_bsg_diag_mode_exit(9)lpfc_sli3_bsg_diag_loopback_mode(9)lpfc_sli4_bsg_set_link_diag_state(9)lpfc_sli4_bsg_set_loopback_mode(9)lpfc_sli4_diag_fcport_reg_setup(9)lpfc_sli4_bsg_diag_loopback_mode(9)lpfc_sli4_bsg_diag_mode_end(9)lpfc_sli4_bsg_link_diag_test(9)lpfcdiag_loop_self_reg(9)lpfcdiag_loop_self_unreg(9)lpfcdiag_loop_get_xri(9)lpfc_bsg_dma_page_alloc(9)lpfc_bsg_dma_page_free(9)lpfc_bsg_dma_page_list_free(9)diag_cmd_data_alloc(9)lpfcdiag_sli3_loop_post_rxbufs(9)lpfc_bsg_diag_loopback_run(9)lpfc_bsg_get_dfc_rev(9)lpfc_bsg_issue_mbox_cmpl(9)lpfc_bsg_check_cmd_access(9)lpfc_bsg_mbox_ext_session_reset(9)lpfc_rd_obj_emb0_handle_job(9)lpfc_bsg_issue_mbox_ext_handle_job(9)lpfc_bsg_issue_read_mbox_ext_cmpl(9)lpfc_bsg_issue_write_mbox_ext_cmpl(9)lpfc_bsg_sli_cfg_read_cmd_ext(9)lpfc_bsg_sli_cfg_write_cmd_ext(9)lpfc_bsg_handle_sli_cfg_mbox(9)lpfc_bsg_mbox_ext_abort(9)lpfc_bsg_read_ebuf_get(9)lpfc_bsg_write_ebuf_set(9)lpfc_bsg_handle_sli_cfg_ebuf(9)lpfc_bsg_handle_sli_cfg_ext(9)lpfc_bsg_issue_mbox(9)lpfc_bsg_mbox_cmd(9)lpfc_check_fwlog_support(9)lpfc_bsg_get_ras_config(9)lpfc_bsg_set_ras_config(9)lpfc_bsg_get_ras_lwpd(9)lpfc_bsg_get_ras_fwlog(9)lpfc_bsg_hst_vendor(9)lpfc_bsg_request(9)lpfc_bsg_timeout(9)
like, that's fifty-nine whole cross-references. fifty-nine!! ate and left no crumbs ππ iykyk.
π real talk though: every single flag, argument, file path and reference up there is exactly as it appears in the original β i did not change one character of the literal stuff, because facts are sacred even when the vibe is immaculate β¨
and that's the page, bestie π mwah π
β cute lil sign-off: this one comes from the source tree at ./drivers/scsi/lpfc, dated October 2026, and it's page lpfc_bsg_diag_loopback_mode(9) in the Kernel API Manual. go forth and dispatch those diag commands ππ¦π
π¦ 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