scsi_block_targets(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

scsi_block_targets β€” transition all SCSI child devices to SDEV_BLOCK state. Yes bestie, this is scsi_block_targets(9) from the Kernel API Manual, and it’s here to put every SCSI child device into SDEV_BLOCK state. It’s giving group chat gets put on do-not-disturb πŸ’….


πŸ¦‹ SYNOPSIS πŸ¦‹

The exact signature, no cap:

void scsi_block_targets (struct Scsi_Host *shost , struct device *dev );

🌸 ARGUMENTS 🌸

  • shost β€” the Scsi_Host to which this device belongs.
  • dev β€” a parent device of one or more scsi_target devices.

πŸ’– DESCRIPTION πŸ’–

Okay so it iterates over all children of dev, and those children should be scsi_target devices. For every one of them, it switches all subordinate scsi devices to SDEV_BLOCK state. Then it waits for ongoing scsi_queue_rq calls to finish. That’s the whole plot, bestie.

May sleep. Yep, it may sleep. Not a drill, just the actual documented vibe 😭.


🚨 NOTE 🚨

dev must not itself be a scsi_target device. That’s the rule. Do not hand it a scsi_target and expect main character energy β€” it’s literally in the note, bestie πŸ™ˆ.

πŸ”₯ SEE ALSO πŸ”₯

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

The whole friend group, every single one:

Bye bestie! From ./drivers/scsi, dated October 2026, on the scsi_block_targets(9) page β€” stay blocked and slay πŸ’…βœ¨

πŸ“¦ where this page comes from