scsi_report_device_reset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scsi_report_device_reset(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual page for scsi_report_device_reset. This one is short, sweet, and very "tell the mid-layer what you just saw" energy. 🫢


🌸 NAME 🌸

scsi_report_device_reset β€” report device reset observed


πŸ› οΈ SYNOPSIS πŸ› οΈ

void scsi_report_device_reset (struct Scsi_Host *shost , int channel ,
       int target );

πŸŽ€ ARGUMENTS πŸŽ€

  • shost β€” the host in question, aka the host we're talking about πŸ’–
  • channel β€” the channel on which the reset was observed
  • target β€” the target on which the reset was observed

πŸ’– DESCRIPTION πŸ’–

This is a utility function that low-level drivers use to report that they have observed a device reset on the device being handled. like, "hey bestie, a reset happened over here" vibes. ✨

Lock status: Host lock must be held πŸ”’

🌈 RETURN 🌈

Nothing β€” that's it, that's the return. literally nothing. πŸ’€


🧚 NOTES 🧚

You only actually need to call this if the reset is one which originates from an unknown location. Resets originated by the mid-level itself don't need to call this, but there should be no harm. πŸ¦‹

The main purpose of this is to make sure that a CHECK_CONDITION is properly treated. so yeah, it's giving "small function, important job" energy. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/scsi/scsi_error.c

the whole squad:


mwah πŸ’‹ that's the whole page, bestie. source/version: ./drivers/scsi, date: October 2026, page: scsi_report_device_reset(9). 🫢

πŸ“¦ where this page comes from