pmcraid_eh_...eset_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, welcome to pmcraid_eh_device_reset_handler from the Kernel API Manual β€” the page-name situation is pmcraid_eh_...eset_handler(9), and the NAME section is giving bus/target/device reset handler callbacks. It's the reset-callback bestie, here for the bus/target/device reset-handler moment. πŸ’…

✨ SYNOPSIS ✨

int pmcraid_eh_device_reset_handler (struct scsi_cmnd *scmd );

πŸŽ€ ARGUMENTS πŸŽ€

  • scmd β€” pointer to the scsi_cmd that was sent to the resource to be reset. That's the command ticket attached to the thing that needs its reset moment. 🎫

πŸ’– DESCRIPTION πŸ’–

All these routines invoke pmcraid_reset_device with the appropriate parameters. (tiny original-page typo moment: "invokve" β€” iconic, but meaning-wise it's invoke.) πŸ’€

Since these are called from the mid-layer EH thread, no other IO will be queued to the resource being reset. So the normal IO queue is not adding more drama while the reset is happening. 🚧

However, the control path (IOCTL) may be active, so it is necessary to synchronize IOARRIN writes. pmcraid_reset_device takes care of that by locking/unlocking host_lock. Lock, unlock, keep it cute. πŸ”

Return value is SUCCESS or FAILED. That's it: slay or no-slay. βœ…βŒ

πŸ¦‹ SEE ALSO πŸ¦‹


And that's the tea πŸ“ β€” the source/version footer says ./drivers/scsi, the date says October 2026, and the footer still reps pmcraid_eh_...eset_handler(9). Stay reset-ready, bestie πŸ’œπŸ«Ά

πŸ“¦ where this page comes from