target_send_busy(9)
π 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 astruct 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. π
transport_init_session(9)transport_alloc_session(9)transport_alloc_session_tags(9)transport_init_session_tags(9)target_cmd_size_check(9)target_init_cmd(9)target_submit_prep(9)target_submit_cmd(9)target_queue_submission(9)target_submit(9)target_submit_tmr(9)target_get_sess_cmd(9)target_put_sess_cmd(9)target_stop_cmd_counter(9)target_stop_session(9)target_wait_for_cmds(9)target_wait_for_sess_cmds(9)transport_wait_for_tasks(9)translate_sense_reason(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms