target_send_busy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… target_send_busy β€” from the Kernel API Manual, bestie ✨

Okay so picture this: you're a kernel target driver, the initiator is asking for something, and honestly? The vibe check says not right now. That's literally what this function is for β€” it sends a SCSI BUSY status right on back to the initiator. No cap. 🫢


πŸŽ€ NAME πŸŽ€

target_send_busy β€” sends the SCSI BUSY status back to the initiator. That's it, that's the whole job, and she does it flawlessly. πŸ‘‘


✨ SYNOPSIS ✨

int target_send_busy(struct se_cmd *cmd);

🌸 ARGUMENTS 🌸

  • cmd β€” the SCSI command you're busting out that BUSY reply for. It's a struct se_cmd *, and yes you have to hand it over, the whole function hinges on it. πŸ’–

πŸ’€ NOTE πŸ’€

Okay this one is important, do not skip it: only call this function if target_submit_cmd*() failed. Like... failed failed. If the submit actually worked, this is not the move, bestie. Read the room. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

The source lives in the kernel file ./drivers/target/target_core_transport.c β€” go say hi, she's iconic. πŸ’œ


And that's the whole page!! 🌈 This lil masterpiece comes to you from ./drivers/target, dated October 2026, and it's serving target_send_busy(9) realness from the Kernel API Manual. Slay, stay busy, and don't call her unless the submit failed. Mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from