PROBE::SCSI.IODISP(3stap)

💅 PROBE::SCSI.IODISP 💅

okay bestie, gather round, because we're talking about probe::scsi.iodispatching — that's the probe from the SCSI Tapset, and yes it's a 3stap situation, the whole SystemTap manual-page vibe, you know the drill 🎀

It's the SCSI mid-layer dispatched low-level SCSI command probe. That's the moment the mid-layer hands a low-level SCSI command off to the driver. It's giving "the baton pass, but make it kernel" 🏃♀️✨

---

✨ SYNOPSIS ✨

probe scsi.iodispatching {}

that's it. no args. no drama. she just arrives. 💅

---

🌸 VALUES 🌸

every one of these lil cuties is available to you inside the probe handler, and yes you want all of them:

• device_state — the current state of the device, right now, as we speak 🫶
• lun — the lun number. the logical unit number, bestie, not a moon 🌙
• device_state_str — the current state of the device, but as a string this time. same tea, different cup ☕
• channel — the channel number 📡
• dev_id — the scsi device id 🔖
• host_no — the host number 🏠
• data_direction — this one's important, so listen up: it specifies whether this command is from/to the device, and it's encoded as 0 (DMA_BIDIRECTIONAL), 1 (DMA_TO_DEVICE), 2 (DMA_FROM_DEVICE), or 3 (DMA_NONE). four little numbers, four whole meanings, no cap 🔢
• req_addr — the current struct request pointer, as a number. she's an address, she's a vibe 🧚
• request_buffer — the request buffer address 📍
• request_bufflen — the request buffer length 📏
• data_direction_str — data direction, as a string. the human-readable remix of data_direction 🌈

---

👀 SEE ALSO 👀

• tapset::scsi(3stap) — go read her, she's the whole family tree 🌳

---

fr fr, nothing here is deprecated or dangerous, it's just a probe doing her job and doing it well. main character energy, honestly 👑

---

and that's the whole page, bestie!! this came to you courtesy of the SystemTap Tapset Reference, and the date on the tin is September 2026 — so if you're reading this from the future, hi, you're doing amazing 💖🌸✨🦋🎀