public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com,
	herbert@gondor.apana.org.au, rml@ximian.com,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: netlink vs kobject_uevent ordering
Date: Thu, 4 Nov 2004 10:05:50 -0800	[thread overview]
Message-ID: <20041104180550.GA16744@kroah.com> (raw)
In-Reply-To: <20041104154317.GA1268@krispykreme.ozlabs.ibm.com>

On Fri, Nov 05, 2004 at 02:43:17AM +1100, Anton Blanchard wrote:
> 
> Hi,
> 
> I noticed kobject_uevent was failing to init on my box. It looks like
> both netlink and kobject_uevent are marked core_initcall and we may not
> do them in the correct order.
> 
> I guess the recent changes to netlink caused this:
> 
> http://linux.bkbits.net:8080/linux-2.5/cset@41896b1dIiNgXpwhgimeurIqPpofbw?nav=index.html|ChangeSet@-2d

Hm, I don't think that patch caused the reversal, it seems like we've
always linked this in the opposite order as my System.map before this
patch went in shows:
	c04b016c t __initcall_kobject_uevent_init
	c04b0170 t __initcall_netlink_proto_init

So, Robert and Kay, any thoughts as to how this has ever worked at boot
time in the past?

thanks,

greg k-h

  reply	other threads:[~2004-11-04 18:13 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 [this message]
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
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=20041104180550.GA16744@kroah.com \
    --to=greg@kroah.com \
    --cc=anton@samba.org \
    --cc=davem@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ximian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox