zfcp_dbf_hba_fsf_reqid(9)
π zfcp_dbf_hba_fsf_reqid β NAME π
okay bestie, welcome to the zfcp_dbf_hba_fsf_reqid(9) page in the Kernel API Manual. This function is here to trace only the tag and a request ID β thatβs the whole assignment, and it ate. π
β¨
β¨ SYNOPSIS β¨
void zfcp_dbf_hba_fsf_reqid (const char *const tag , const int level ,
struct zfcp_adapter *const adapter , const u64 req_id );
π ARGUMENTS π
tagβ the tag documenting the source. Itβs giving βwhere did this come fromβ energy, fr fr. π¦levelβ the trace level. Yep, thatβs the level, no cap.adapterβ the adapter instance the request ID belongs to. Keep βem matched, bestie. πreq_idβ the request ID to trace. This is literally the ID being traced, periodt. πΈ
π SEE ALSO π
Kernel file: ./drivers/s390/scsi/zfcp_dbf.c.
The whole zfcp dbf friend group is here too:
zfcp_dbf_hba_fsf_res(9)zfcp_dbf_hba_fsf_fces(9)zfcp_dbf_hba_fsf_uss(9)zfcp_dbf_hba_uas(9)zfcp_dbf_hba_bit_err(9)zfcp_dbf_hba_def_err(9)zfcp_dbf_rec_trig(9)zfcp_dbf_rec_trig_lock(9)zfcp_dbf_rec_run_lvl(9)zfcp_dbf_rec_run(9)zfcp_dbf_rec_run_wka(9)zfcp_dbf_san_req(9)zfcp_dbf_san_res(9)zfcp_dbf_san_in_els(9)zfcp_dbf_scsi_common(9)zfcp_dbf_scsi_eh(9)zfcp_dbf_adapter_register(9)zfcp_dbf_adapter_unregister(9)
mwah π this lil page comes from ./drivers/s390/scsi, dated October 2026, and itβs the zfcp_dbf_hba_fsf_reqid(9) manual page. xoxo, your local kernel bestie π«Άπ
π¦ 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