STRUCT ZFCP_DBF_SCSI(9)
π struct zfcp_dbf_scsi(9) β like, the Kernel API Manual, bestie π
okay so picture this: it's a page from the Kernel API Manual, and it's all about struct zfcp_dbf_scsi β the shared trace record for SCSI records. yes, THE one. she's the blueprint for how SCSI tracing gets written down, and honestly? iconic. β¨
πΈ NAME πΈ
struct zfcp_dbf_scsi β the common trace record for SCSI records, fr fr. not a vibe, a structure. π
π¦ SYNOPSIS π¦
here's the whole glow-up, laid out exactly as she comes:
struct zfcp_dbf_scsi {
u8 id;
char tag[ZFCP_DBF_TAG_LEN];
u32 scsi_id;
u32 scsi_lun;
u32 scsi_result;
u8 scsi_retries;
u8 scsi_allowed;
u8 fcp_rsp_info;
#define ZFCP_DBF_SCSI_OPCODE 16;
u8 scsi_opcode[ZFCP_DBF_SCSI_OPCODE];
u64 fsf_req_id;
u64 host_scribble;
u16 pl_len;
struct fcp_resp_with_ext fcp_rsp;
u32 scsi_lun_64_hi;
};
and yes, that #define ZFCP_DBF_SCSI_OPCODE 16; really does live inside the struct like that, semicolon and all. not me judging, she's just quirky like that π
π Members π
okay bestie, field-by-field tour, let's go:
idβ the unique number of the recovery record type. her little ID card, basically πtagβ an identifier string specifying the location of initiation. like a "you are here" sticker but for tracing πscsi_idβ the scsi device idscsi_lunβ the scsi device logical unit number, low part of 64 bit, old 32 bit. yes she's the low half, she's the vintage half π§scsi_resultβ the scsi resultscsi_retriesβ the current retry number of the scsi request. we've all been there, keep trying queen πscsi_allowedβ the allowed retries. aka the limit, the boundary, the ceilingfcp_rsp_infoβ the FCP response info codescsi_opcodeβ the scsi opcodefsf_req_idβ the request id of the fsf requesthost_scribbleβ LLD specific data attached to the SCSI request. the name?? unhinged. the job?? essential ποΈpl_lenβ the length of the payload stored aszfcp_dbf_payfcp_rspβ the response for the FCP requestscsi_lun_64_hiβ the scsi device logical unit number, high part of 64 bit. the other half of the 64-bit duo, reunited at last π«Ά
β SEE ALSO β
first up, the source of truth itself: Kernel file ./drivers/s390/scsi/zfcp_dbf.h struct. go read it, iykyk π
and then the whole extended friend group, no one left out:
zfcp_dbf_rec_trigger(9)struct zfcp_dbf_rec_running(9)enum zfcp_dbf_rec_id(9)struct zfcp_dbf_rec(9)enum zfcp_dbf_san_id(9)struct zfcp_dbf_hba_res(9)struct zfcp_dbf_hba_uss(9)struct zfcp_dbf_hba_uas(9)struct zfcp_dbf_hba_fces(9)enum zfcp_dbf_hba_id(9)struct zfcp_dbf_hba(9)enum zfcp_dbf_scsi_id(9)struct zfcp_dbf_pay(9)struct zfcp_dbf(9)zfcp_dbf_hba_fsf_resp_suppress(9)zfcp_dbf_hba_fsf_response(9)zfcp_dbf_scsi_result(9)zfcp_dbf_scsi_fail_send(9)zfcp_dbf_scsi_abort(9)zfcp_dbf_scsi_devreset(9)zfcp_dbf_scsi_nullcmnd(9)
ngl this page lowkey ate. go forth and trace those SCSI records, bestie, you've got this πβ¨
and that's the whole page, mwah π β brought to you from ./drivers/s390/scsi, dated October 2026, filed under struct zfcp_dbf_scsi(9). 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