scsi_add_single_device(9)

✨ scsi_add_single_device(9) ✨

okay so bestie, welcome to the scsi_add_single_device page from the Kernel API Manual 💅 no cap, this one's a little cutie — it's the function that answers when a user asks the kernel to go find a SCSI device. let's get into it 🫶

---

🌸 SYNOPSIS 🌸

int scsi_add_single_device (uint host , uint channel , uint id , uint lun );

four uint args, one int coming back at you. slay ✨

🎀 ARGUMENTS 🎀

• host — a user-supplied decimal integer, periodt.
• channel — a user-supplied decimal integer, fr fr.
• id — a user-supplied decimal integer, no cap.
• lun — a user-supplied decimal integer, iconic.

like yes they're all the same description, that's literally what the page says and we respect it 💀 all four are decimal integers that came from the user.

💖 DESCRIPTION 💖

so the way this gets called is lowkey iconic: the user writes "scsi add-single-device" to /proc/scsi/scsi, and that's what triggers it. iykyk 🦋

once it's in there, it does a scsi_host_lookup, and then it's giving two possible paths:

• it calls user_scan if that transport type supports it 🔥
• or else it falls back to scsi_scan_host_selected ✨

either way, the device gets probed/added. main character energy honestly 👑

⭐ NOTE ⭐

heads up bestie — this seems to be aimed exclusively at SCSI parallel busses. like, that's the vibe check and it passed 🌈

🌸 SEE ALSO 🌸

go look at the kernel file ./drivers/scsi/scsi_proc.c first, and then the whole friend group:

• struct scsi_proc_entry(9)
• scsi_template_proc_dir(9)
• scsi_proc_hostdir_add(9)
• scsi_proc_hostdir_rm(9)
• scsi_proc_host_add(9)
• scsi_proc_host_rm(9)
• proc_print_scsidevice(9)
• scsi_remove_single_device(9)
• proc_scsi_write(9)
• proc_scsi_open(9)
• scsi_init_procfs(9)
• scsi_exit_procfs(9)

---

🫶 and that's the whole page!! this one lives out of ./drivers/scsi, dated October 2026 — so when you see that version/date in the footer, that's just the page being its cute self. mwah 💋 go add some devices bestie ✨🎀