From: Daniel Walker <dwalker@mvista.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
Simon Arlott <simon@fire.lp0.eu>,
Rene Herman <rene.herman@keyaccess.nl>,
Neil Brown <neilb@suse.de>
Subject: Re: [patch 2/4] fastboot: retry mounting the root fs if we can't find init
Date: Sun, 20 Jul 2008 18:35:04 -0700 [thread overview]
Message-ID: <1216604104.14562.3.camel@dhcp32.mvista.com> (raw)
In-Reply-To: <20080720151304.59b06786@infradead.org>
On Sun, 2008-07-20 at 15:13 -0700, Arjan van de Ven wrote:
> + /*
> + * We haven't found init yet... potentially because the device
> + * is still being probed. We need to
> + * - flush keventd and friends
> + * - wait for the known devices to complete their probing
> + * - try to mount the root fs again
> + */
> + flush_scheduled_work();
> + while (driver_probe_done() != 0)
> + msleep(100);
I realize the while() loop above is just code shifted from
init/do_mounts_md.c , but I'm wondering if that could be a complete
instead of a while then sleep 100ms .. That would reduce the overshoot .
Daniel
next prev parent reply other threads:[~2008-07-21 1:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080720151140.4aa7c682@infradead.org>
2008-07-20 22:12 ` [patch 1/4] fastboot: make fastboot a config option Arjan van de Ven
2008-07-30 15:23 ` Randy Dunlap
2008-07-31 10:53 ` Ingo Molnar
2008-07-20 22:13 ` [patch 2/4] fastboot: retry mounting the root fs if we can't find init Arjan van de Ven
2008-07-21 1:35 ` Daniel Walker [this message]
2008-07-20 22:13 ` [patch 3/4] fastboot: make the raid autodetect code wait for all devices to init Arjan van de Ven
2008-07-20 23:06 ` Neil Brown
2008-07-20 23:12 ` david
2008-07-20 23:19 ` Arjan van de Ven
2008-07-20 23:31 ` Arjan van de Ven
2008-07-21 4:30 ` Neil Brown
2008-07-20 21:33 ` Arjan van de Ven
2008-07-20 22:14 ` [patch 4/4] fastboot: remove "wait for all devices before mounting root" delay Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1216604104.14562.3.camel@dhcp32.mvista.com \
--to=dwalker@mvista.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=rene.herman@keyaccess.nl \
--cc=simon@fire.lp0.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox