lkml.org 
[lkml]   [2006]   [Apr]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch] ipv4: initialize arp_tbl rw lock
    Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
    >
    > Ok, so the problem seems to be that inet_init gets called after qeth_init.
    > Looking at the top level Makefile this seems to be true for all network
    > drivers in drivers/net/ and drivers/s390/net/ since we have
    >
    > vmlinux-main := $(core-y) $(libs-y) $(drivers-y) $(net-y)
    >
    > The patch below works for me... I guess there must be a better way to make
    > sure that any networking driver's initcall is made before inet_init?
    >
    > Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
    > ---
    >
    > Makefile | 2 +-
    > 1 file changed, 1 insertion(+), 1 deletion(-)
    >
    > diff --git a/Makefile b/Makefile
    > index b401942..c5cea07 100644
    > --- a/Makefile
    > +++ b/Makefile
    > @@ -567,7 +567,7 @@ #
    > # System.map is generated to document addresses of all kernel symbols
    >
    > vmlinux-init := $(head-y) $(init-y)
    > -vmlinux-main := $(core-y) $(libs-y) $(drivers-y) $(net-y)
    > +vmlinux-main := $(core-y) $(libs-y) $(net-y) $(drivers-y)

    <wonders what this will break>

    I have a bad feeling that one day we're going to come unstuck with this
    practice. Is there anything which dictates that the linker has to lay
    sections out in .o-file-order?

    Perhaps net initcalls should be using something higher priority than
    device_initcall().
    -
    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: 2006-04-08 12:17    [W:0.026 / U:1.140 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site