linux-kernel - [PATCH] Allow SCSI_WAIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1226585472-12559-1-git-send-email-bwalle@suse.de>
Date:	Thu, 13 Nov 2008 15:11:12 +0100
From:	Bernhard Walle <bwalle@...e.de>
To:	James.Bottomley@...elEye.com
Cc:	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Bernhard Walle <bwalle@...e.de>
Subject: [PATCH] Allow SCSI_WAIT_SCAN to be deselected

This patch adds a proper help for SCSI_WAIT_SCAN and allows the module to be
deselected. I see no reason to force it being build. It also makes it
impossible to compile-in the module.


Signed-off-by: Bernhard Walle <bwalle@...e.de>
---
 drivers/scsi/Kconfig |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index 403ecad..42b8355 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -257,10 +257,15 @@ config SCSI_SCAN_ASYNC
 	  or async on the kernel's command line.
 
 config SCSI_WAIT_SCAN
-	tristate
+	tristate "Module to wait until all the async scans are complete"
 	default m
-	depends on SCSI
-	depends on MODULES
+	depends on SCSI && m
+    help
+      This is a simple module to 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 busses before
+      allowing the boot to proceed
 
 menu "SCSI Transports"
 	depends on SCSI
-- 
1.6.0.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/