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

Date:	Sun, 29 Mar 2009 19:23:15 +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:
>> 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)?
> 
> in part.
> 
> The problem with USB probing is that devices come online whenever they
> feel like it; there is no way to wait for that.

Yes, that is a problem when trying to make bootable USB pen drives.

>> Can I load that module before loading the actual SCSI/SATA/PATA
>> driver?
> 
> it's the loading of the driver that causes the wait. Not the act
> of having the driver loaded.
> 
> so the way to wait for things to settle is to load the driver...
> 
> ... I take it the answer to your question is "no". Yes you can load it
> earlier, but no it has no effect. You can however load/unload it
> multiple times.

I understand the logic now, works as expected on my machine. Many thanks 
for your quick help.


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