sd_eh_action(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sd_eh_action(9) — like, the error handling callback, bestie

Ok so real talk, this one's from the Kernel API Manual (sd_eh_action, section 9) and it's genuinely one of those tiny-but-iconic functions. Let's get into it 🎀

✨ NAME ✨

sd_eh_action — the error handling callback. That's it, that's the whole vibe. She's the one who picks up the phone when a command fails 😭

🌸 SYNOPSIS 🌸

int sd_eh_action (struct scsi_cmnd *scmd , int eh_disp );

Look at her. Two args, one int return. Clean. Minimalist. Main character energy fr fr 👑

🦋 ARGUMENTS 🦋

  • scmd — the sd-issued command that has failed. Like, the thing that went 💀
  • eh_disp — the recovery disposition that the midlayer suggested. Basically the midlayer's hot take on how to recover 🌈

💖 DESCRIPTION 💖

So here's the situation, bestie. This function gets called by the SCSI midlayer upon completion of an error test command (currently TEST UNIT READY — ok noted, that's the one 👀). The result of sending the eh command gets passed in through eh_disp.

And what are we even looking for? We're hunting for devices that fail medium access commands but are totally OK with non-access commands like test unit ready. Because if that happens, the recovery wrongly sees the device as having a successful recovery — like, no cap, it looks like a slay but it's actually a lie 🙈

So yeah, she's the vibe check for fake-successful recoveries. Periodt. 💅

👑 SEE ALSO 👑

Kernel file ./drivers/scsi/sd.c plus the whole friend group:

And that's the whole page, gorgeous 🫶 This lil legend lives in ./drivers/scsi and the docs are dated October 2026 — so mark your calendars, mwah 💋⭐

📦 where this page comes from