zfcp_dbf_rec_run_wka(9)

💫 zfcp_dbf_rec_run_wka(9) — a little kernel API manual page, but make it make sense 💫

okay so bestie, welcome to the zfcp_dbf_rec_run_wka(9) glow-up ✨ this is straight-up Kernel API Manual territory, and it's basically about one tiny function that leaves a lil paper trail 🎀

---

✨ NAME ✨

zfcp_dbf_rec_run_wka — trace a wka port event, and it comes with the good info like the running recovery 💅

---

🌸 SYNOPSIS 🌸

void zfcp_dbf_rec_run_wka (char *tag , struct zfcp_fc_wka_port *wka_port , u64 req_id );

like… it returns void, so don't go looking for a return value, she doesn't do that 👑 no cap.

---

🦋 ARGUMENTS 🦋

• tag — the identifier for the event 🏷️ so you know which thing you're looking at, iykyk
• wka_port — the well known address port 💖 literally a struct zfcp_fc_wka_port *, so it's the wka port in question
• req_id — the request ID, and its whole job is to correlate with a potential HBA trace record 🔥 like a little matching friendship bracelet between records fr fr

---

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/s390/scsi/zfcp_dbf.c 📁 and honestly? the whole friend group is here, go say hi 💜

• 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_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)

bestie this is a long list and every single one of them is here, no skipping 🙈 that's the whole squad, periodt.

---

and that's the page!! 🫶 ok final vibe check before you close the tab: this cutie lives in ./drivers/s390/scsi, dated October 2026, and the whole thing answers to the name zfcp_dbf_rec_run_wka(9) 💀✨ slay, go trace something 💅🍓