[PATCH] SCSI: explain the hidden scsi_wait_scan Kconfig variable
From: Stefan Richter
Date: Wed Jun 17 2009 - 06:07:47 EST
People keep sending patches to expose CONFIG_SCSI_WAIT_SCAN as a tunable
item. These patches aren't accepted upstream, so let's stop the ongoing
irritation of people due to this obscure and strange installed module
and its Kconfig option.
Signed-off-by: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>
drivers/scsi/Kconfig | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
@@ -259,10 +259,25 @@ config SCSI_SCAN_ASYNC
or async on the kernel's command line.
+ tristate # No prompt here, this is a hidden option.
depends on SCSI
depends on MODULES
+ Wait until all the async scans are complete. The idea is to use
+ it in initrd/ initramfs scripts. You modprobe it after all the
+ modprobes of the root SCSI drivers and it will wait until they
+ have all finished scanning their buses before allowing the boot
+ to proceed.
+ Of course this does not work if targets boot independently of and
+ in parallel with the initiator, and/ or with transports with non-
+ deterministic target discovery schemes, and/ or if a transport
+ driver does not support scsi_wait_scan.
+ Still, this option is not exposed as a prompt because little is
+ to be gained by disabling it, whereas people who accidentally
+ switch it off may wonder why their mkinitrd gets into trouble.
menu "SCSI Transports"
depends on SCSI
-=====-==--= -==- =---=
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/