From: Rik van Riel <riel@redhat.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] wait for devices before continuing
Date: Fri, 11 Aug 2006 16:11:50 -0400 [thread overview]
Message-ID: <44DCE486.2040508@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
This patch fixes the "could not found the root filesystem after
the blkfront driver was loaded" race condition, which can occur
if blkfront does not get the disk hooked up before mount, or the
lvm tools, have already run.
It does this by simply waiting for all xenbus devices (which
have drivers loaded) to be attached to the driver before
continuing after the module initialization.
I have test booted this a number of times and the bootup race
condition appears to be gone.
Signed-off-by: Rik van Riel <riel@redhat.com>
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
[-- Attachment #2: linux-2.6-xen-xenbus-wait.patch --]
[-- Type: text/x-patch, Size: 2413 bytes --]
--- linux-2.6.17.noarch/drivers/xen/blkfront/blkfront.c.waitforme 2006-08-11 14:01:58.000000000 -0400
+++ linux-2.6.17.noarch/drivers/xen/blkfront/blkfront.c 2006-08-11 14:02:27.000000000 -0400
@@ -824,10 +824,17 @@ static struct xenbus_driver blkfront = {
static int __init xlblk_init(void)
{
+ int ret;
+
if (!is_running_on_xen())
return -ENODEV;
- return xenbus_register_frontend(&blkfront);
+ ret = xenbus_register_frontend(&blkfront);
+ if (ret)
+ return ret;
+
+ xenbus_wait_for_devices();
+ return 0;
}
module_init(xlblk_init);
--- linux-2.6.17.noarch/drivers/xen/netfront/netfront.c.waitforme 2006-08-11 14:02:41.000000000 -0400
+++ linux-2.6.17.noarch/drivers/xen/netfront/netfront.c 2006-08-11 14:03:19.000000000 -0400
@@ -1579,6 +1579,8 @@ static struct notifier_block notifier_in
static int __init netif_init(void)
{
+ int ret;
+
if (!is_running_on_xen())
return -ENODEV;
@@ -1589,7 +1591,12 @@ static int __init netif_init(void)
(void)register_inetaddr_notifier(¬ifier_inetdev);
- return xenbus_register_frontend(&netfront);
+ ret = xenbus_register_frontend(&netfront);
+ if (ret)
+ return ret;
+
+ xenbus_wait_for_devices();
+ return 0;
}
module_init(netif_init);
--- linux-2.6.17.noarch/drivers/xen/xenbus/xenbus_probe.c.waitforme 2006-08-11 13:59:37.000000000 -0400
+++ linux-2.6.17.noarch/drivers/xen/xenbus/xenbus_probe.c 2006-08-11 14:00:35.000000000 -0400
@@ -1067,7 +1067,7 @@ static int print_device_status(struct de
* boot slightly, but of course needs tools or manual intervention to set up
* those flags correctly.
*/
-static int __init wait_for_devices(void)
+int xenbus_wait_for_devices(void)
{
unsigned long timeout = jiffies + 10*HZ;
@@ -1083,4 +1083,5 @@ static int __init wait_for_devices(void)
return 0;
}
-late_initcall(wait_for_devices);
+EXPORT_SYMBOL(xenbus_wait_for_devices);
+late_initcall(xenbus_wait_for_devices);
--- linux-2.6.17.noarch/include/xen/xenbus.h.waitforme 2006-08-11 14:00:07.000000000 -0400
+++ linux-2.6.17.noarch/include/xen/xenbus.h 2006-08-11 14:01:31.000000000 -0400
@@ -157,6 +157,7 @@ int register_xenbus_watch(struct xenbus_
void unregister_xenbus_watch(struct xenbus_watch *watch);
void xs_suspend(void);
void xs_resume(void);
+int xenbus_wait_for_devices(void);
/* Used by xenbus_dev to borrow kernel's store connection. */
void *xenbus_dev_request_and_reply(struct xsd_sockmsg *msg);
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-08-11 20:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44DCE486.2040508@redhat.com \
--to=riel@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.