linux-kernel - Re: Possible bug in SCSI Kconfig

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-prev] [day] [month] [year] [list]

Date:	Thu, 23 Oct 2008 20:59:53 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Matthew Wilcox <matthew@....cx>
CC:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Fabio Comolli <fabio.comolli@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	sam@...nborg.org, linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: Possible bug in SCSI Kconfig

Matthew Wilcox wrote:
> On Thu, Oct 23, 2008 at 07:30:33PM +0200, Stefan Richter wrote:
>>   - scsi_wait_scan is a special method to wait for devices during boot
>>     which only works with some hardware types.  More general methods are
>>     available and have been in use far longer than scsi_wait_scan
>>     exists.  Nobody fundamentally needs scsi_wait_scan, it is only a
>>     convenient tool for some users who choose to use it.
>>     Special features are traditionally per default off in Kconfig and
>>     are supposed to be actively enabled.
> 
> What 'general methods' would those be?

Waiting for the desired numbers of devices to show up.  Or for a known 
device.

scsi_wait_scan is optimal though if it is known at the outset how many 
devices (or how many at maximum) will show up.
-- 
Stefan Richter
-=====-==--- =-=- =-===
http://arcgraph.de/sr/
--
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/