linux-kernel - Re: CONFIG_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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Mar 2007 18:16:14 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	James Bottomley <James.Bottomley@...elEye.com>
cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: CONFIG_SCSI_WAIT_SCAN=m

On Tue, 27 Mar 2007, James Bottomley wrote:
> On Tue, 2007-03-27 at 17:25 +0100, Hugh Dickins wrote:
> > I'm not using an initrd, most of my kernel is builtin,
> > just a few modules for occasional filesystems.
> > 
> > CONFIG_MODULES=y
> > CONFIG_SCSI=y
> > CONFIG_SCSI_SCAN_ASYNC=y
> > CONFIG_SCSI_WAIT_SCAN=m
> > 
> > 2.6.21-rc5-mm2 VFS panics unable to find my root on /dev/sda2,
> > but boots okay if I change drivers/scsi/Kconfig to "default y"
> > instead of "default m" for SCSI_WAIT_SCAN.
> 
> Hmm ... it sounds like there's a missing scsi_complete_async_scans() in
> your environment?  What's your configuration ... which SCSI drivers, and
> which are modules?

Fusion MPT: neither that nor the rest of SCSI modular (apart from this
infamous SCSI_WAIT_SCAN).  Full .config attached.

> 
> scsi_wait_async_scan is supposed to be unnecessary unless you have
> modular SCSI drivers that the initrd needs to wait for root on.
View attachment "flowers_config" of type "TEXT/PLAIN" (31888 bytes)