lpfc_idiag_cmd_get(9)
π lpfc_idiag_cmd_get(9)
okay so bestie, welcome to the Kernel API Manual page for lpfc_idiag_cmd_get β yes the title and the manual name are literally the same thing twice, that's just how manpages roll, don't @ me. β¨
πΈ NAME
lpfc_idiag_cmd_get β get and parse idiag debugfs commands from user space π«Ά
β SYNOPSIS
int lpfc_idiag_cmd_get (const char __user *buf , size_t nbytes , struct
lpfc_idiag_cmd *idiag_cmd );
π ARGUMENTS
bufβ the pointer to the user space buffer. like, the actual data lives over there in userspace land πnbytesβ the number of bytes in that user space buffer. how much we're reading, bestie πidiag_cmdβ pointer to theidiag_cmdcommand struct. this is where the parsed stuff goes π¦
π₯ DESCRIPTION
So this routine reads data from the debugfs user space buffer and parses that buffer to get the idiag command and its arguments. The "while space" in between the set of data is used as the parsing separator β and yes the manpage literally calls it "while space" (iconic typo fr fr, we all know it means whitespace π). Anyway: spaces between chunks = the split points. That's the whole vibe.
This routine returns 0 when successful, and it returns the proper error code back to the user space when things go sideways. no cap, that's the contract π
ngl, this one's a parser β if your input is weird, expect a non-zero return and go touch some grass, then try again π
π SEE ALSO
The kernel file this lives in, obviously:
./drivers/scsi/lpfc/lpfc_debugfs.c
and like, the whole extended friend group π:
lpfc_debugfs_disc_trc_data(9)lpfc_debugfs_slow_ring_trc_data(9)lpfc_debugfs_hbqinfo_data(9)lpfc_debugfs_commonxripools_data(9)lpfc_debugfs_multixripools_data(9)lpfc_debugfs_lockstat_data(9)lpfc_debugfs_dumpHBASlim_data(9)lpfc_debugfs_dumpHostSlim_data(9)lpfc_debugfs_nodelist_data(9)lpfc_debugfs_nvmestat_data(9)lpfc_debugfs_scsistat_data(9)lpfc_debugfs_ioktime_data(9)lpfc_debugfs_nvmeio_trc_data(9)lpfc_debugfs_hdwqstat_data(9)lpfc_debugfs_disc_trc(9)lpfc_debugfs_slow_ring_trc(9)lpfc_debugfs_nvme_trc(9)lpfc_debugfs_disc_trc_open(9)lpfc_debugfs_slow_ring_trc_open(9)lpfc_debugfs_hbqinfo_open(9)lpfc_debugfs_multixripools_open(9)lpfc_debugfs_lockstat_open(9)lpfc_debugfs_ras_log_open(9)lpfc_debugfs_dumpHBASlim_open(9)lpfc_debugfs_dumpHostSlim_open(9)lpfc_debugfs_nodelist_open(9)lpfc_debugfs_lseek(9)lpfc_debugfs_read(9)lpfc_debugfs_release(9)lpfc_debugfs_multixripools_write(9)lpfc_idiag_open(9)lpfc_idiag_release(9)lpfc_idiag_cmd_release(9)lpfc_idiag_pcicfg_read(9)lpfc_idiag_pcicfg_write(9)lpfc_idiag_baracc_read(9)lpfc_idiag_baracc_write(9)lpfc_idiag_queinfo_read(9)lpfc_idiag_que_param_check(9)lpfc_idiag_queacc_read_qe(9)lpfc_idiag_queacc_read(9)lpfc_idiag_queacc_write(9)lpfc_idiag_drbacc_read_reg(9)lpfc_idiag_drbacc_read(9)lpfc_idiag_drbacc_write(9)lpfc_idiag_ctlacc_read_reg(9)lpfc_idiag_ctlacc_read(9)lpfc_idiag_ctlacc_write(9)lpfc_idiag_mbxacc_get_setup(9)lpfc_idiag_mbxacc_read(9)lpfc_idiag_mbxacc_write(9)lpfc_idiag_extacc_avail_get(9)lpfc_idiag_extacc_alloc_get(9)lpfc_idiag_extacc_drivr_get(9)lpfc_idiag_extacc_write(9)lpfc_idiag_extacc_read(9)lpfc_debugfs_initialize(9)lpfc_debugfs_terminate(9)lpfc_debug_dump_all_queues(9)
and that's the page, bestie!! π
quick sign-off: this lil masterpiece comes from the source tree at ./drivers/scsi/lpfc, dated October 2026, and it's filed under lpfc_idiag_cmd_get(9) β mwah, slay, periodt ππ¦π
π¦ 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