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: <ac3eb2510903301142h21dec2eajd03057095aa4f11c@mail.gmail.com>
Date:	Mon, 30 Mar 2009 20:42:36 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Dan Williams <dan.j.williams@...el.com>
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?

On Mon, Mar 30, 2009 at 20:23, Dan Williams <dan.j.williams@...el.com> wrote:

> settle: allow --timeout=0 to test for "queue busy"

> +       if (!udev_queue_get_queue_is_empty(udev_queue))
> +               rc = 1;

You mean, we should not wait? Then we need to check for timeout == 0
and return immediately instead of entering the checking loop at all,
right?

Thanks,
Kay
--
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/