lkml.org 
[lkml]   [2004]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: netlink vs kobject_uevent ordering
    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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:07    [W:3.979 / U:0.092 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site