linux-kernel - Re: fastboot/async and initramfs: How am I supposed to know when devices are finished initializing?

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]

Message-id: <49CFA436.5080000@archlinux.org>
Date:	Sun, 29 Mar 2009 18:39:18 +0200
From:	Thomas Bächler <thomas@...hlinux.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Thomas Bächler <thomas@...hlinux.org>,
	linux-kernel@...r.kernel.org
Subject: Re: fastboot/async and initramfs: How am I supposed to know when
 devices are finished initializing?

Arjan van de Ven schrieb:
>> Among other things, this loads the ata_piix on my machine. On older 
>> kernels I could assume that after these commands, /dev/sda* existed
> 
> not if you have CONFIG_SCSI_SCAN_ASYNC set though..
> 
>> and I could immediately access them (in my case, I run cryptsetup on 
>> /dev/sda6). But now, the devices don't exist here, but are only
>> created a second or so later. As a result, the initramfs script has
>> already bailed out as it couldn't find /dev/sda6 and assumed that the
>> hard drive didn't exist.
> 
> the CONFIG_SCSI_WAIT_SCAN method (basically loading that module to wait
> for the scans to finish) will work for you......

Thanks, I will integrate that into our initramfs. Will that also work 
for USB mass storage (which was already problematic with older kernels, 
you load the module you don't know how long it takes until the sdX 
devices are created)?
Can I load that module before loading the actual SCSI/SATA/PATA driver?


Download attachment "signature.asc" of type "application/pgp-signature" (261 bytes)