zfcp_dbf_rec_trig(9)

📦 version 7.3.1, in nixpkgs unstable

💅 zfcp_dbf_rec_trig(9) — like, the kernel API manual bestie ✨

okay so this is a page from the Kernel API Manual, and the function we're obsessing over today is zfcp_dbf_rec_trig 🎀 — no cap, she's the one who traces the events related to a triggered recovery. main character energy fr fr.

🦋 NAME

zfcp_dbf_rec_trig — trace event related to triggered recovery 💫

🌸 SYNOPSIS

void zfcp_dbf_rec_trig (char *tag , struct zfcp_adapter *adapter ,
       struct zfcp_port *port , struct scsi_device *sdev , u8 want , u8 need );

like, that's the whole signature bestie — void, six args, we move 💅

✨ ARGUMENTS

  • tag — the identifier for the event 🏷️ like, the lil name tag so you know which event this is
  • adapter — the adapter on which the erp_action should run 🖥️
  • port — the remote port involved in the erp_action 🔌
  • sdev — the scsi device involved in the erp_action 💾
  • want — the wanted erp_action 👀 (what we want)
  • need — the required erp_action ‼️ (what we actually need)

🎀 DESCRIPTION

okay so the vibe check here: adapter->erp_lock has to be held 🔒 like, that's not optional, that's the whole prerequisite, periodt.

no lock held? that's a you problem bestie, hold adapter->erp_lock first 🙈

🔥 SEE ALSO

the kernel file ./drivers/s390/scsi/zfcp_dbf.c and honestly her whole friend group 🫶:

and that's the post 🫶 this lil masterpiece lives in ./drivers/s390/scsi and it's stamped October 2026 — zfcp_dbf_rec_trig(9) out 💜✨ ily, go hold that lock 🎀

📦 where this page comes from