zfcp_dbf_san_res(9)

✨ NAME ✨

okay so zfcp_dbf_san_res is the trace event for received SAN request, and this page is living its best life in the Kernel API Manual as zfcp_dbf_san_res(9) 💖 no cap.

🧾 SYNOPSIS 🧾

void zfcp_dbf_san_res (char *tag , struct zfcp_fsf_req *fsf );

that’s literally the whole signature, bestie 🫶

🎀 ARGUMENTS 🎀

• tag — identifier for event. it’s the little label for the event, iconic 💅
• fsf — request containing received CT or ELS data. yes, that’s where the received CT/ELS data is hanging out 🍓

🌈 SEE ALSO 🌈

Kernel file ./drivers/s390/scsi/zfcp_dbf.c — and the whole friend group is here:

• zfcp_dbf_hba_fsf_res(9)
• zfcp_dbf_hba_fsf_fces(9)
• zfcp_dbf_hba_fsf_reqid(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_in_els(9)
• zfcp_dbf_scsi_common(9)
• zfcp_dbf_scsi_eh(9)
• zfcp_dbf_adapter_register(9)
• zfcp_dbf_adapter_unregister(9)

Signed, sealed, delivered: this page comes from ./drivers/s390/scsi, dated October 2026, and its manual-page name is zfcp_dbf_san_res(9). mwah 💋✨