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: <49CFB553.1020800@archlinux.org>
Date:	Sun, 29 Mar 2009 19:52:19 +0200
From:	Thomas Bächler <thomas@...hlinux.org>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Thomas Bächler <thomas@...hlinux.org>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: fastboot/async and initramfs: How am I supposed to know when
	devices are finished initializing?

Kay Sievers schrieb:
> In initramfs, you have to wait until the device shows up, not for a
> random module to initialize, or a bus to be scanned -- that can never
> work correctly, it's pure luck, that your logic was always slower than
> the kernel.
> 
> You need a block device -- so you should just wait for the block
> device, instead of making assumptions about initialization of drivers
> or buses. :)

I am planning to do that but there is one problem: Usually, the user 
specifies a root device, or a device that I want to open with 
cryptsetup, or anything similar and I can wait until it shows up.

For lvm however, the user does not specify a specific block device that 
I can wait for, instead lvm scans all available block devices. Now, how 
do I know that the block device that contains my physical volume is 
already there? Maybe I have several hard drives, and several volume 
groups, so should I now call vgchange -ay again and again until the 
right volume group shows up?

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