From: Robert Love <rml@novell.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <greg@kroah.com>, Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org, davem@redhat.com,
herbert@gondor.apana.org.au
Subject: Re: [patch] kobject_uevent: fix init ordering
Date: Thu, 04 Nov 2004 14:11:17 -0500 [thread overview]
Message-ID: <1099595477.31022.148.camel@betsy.boston.ximian.com> (raw)
In-Reply-To: <1099595042.8249.23.camel@localhost.localdomain>
On Thu, 2004-11-04 at 20:04 +0100, Kay Sievers wrote:
Hey, Kay.
> Looks good. Don't know why this never failed on any kernel I used.
> Does the failure happens on a SMP kernel?
In the original patches, I had the initialization done as module_init(),
which is done very late in the init ordering. At some point it was
changed to core_initcall(), which is the very first things initialized.
> > static int send_uevent(const char *signal, const char *obj, const void *buf,
> > - int buflen, int gfp_mask)
> > + int buflen, int gfp_mask)
Ugh. I am sure Greg can sort it out, but following patch has just the
init call ordering change.
Robert Love
fix kobject_uevent init ordering
lib/kobject_uevent.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff -urN linux-2.6.10-rc1/lib/kobject_uevent.c linux/lib/kobject_uevent.c
--- linux-2.6.10-rc1/lib/kobject_uevent.c 2004-10-25 16:17:09.000000000 -0400
+++ linux/lib/kobject_uevent.c 2004-11-04 13:20:32.731836880 -0500
@@ -149,7 +147,7 @@
return 0;
}
-core_initcall(kobject_uevent_init);
+postcore_initcall(kobject_uevent_init);
#else
static inline int send_uevent(const char *signal, const char *obj,
next prev parent reply other threads:[~2004-11-04 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 15:43 netlink vs kobject_uevent ordering Anton Blanchard
2004-11-04 18:05 ` Greg KH
2004-11-04 18:13 ` Robert Love
2004-11-04 19:32 ` David S. Miller
2004-11-04 18:27 ` [patch] kobject_uevent: fix init ordering Robert Love
2004-11-04 19:04 ` Kay Sievers
2004-11-04 19:11 ` Robert Love [this message]
2004-11-04 19:28 ` Robert Love
2004-11-04 20:07 ` Greg KH
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=1099595477.31022.148.camel@betsy.boston.ximian.com \
--to=rml@novell.com \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=greg@kroah.com \
--cc=herbert@gondor.apana.org.au \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®