Re: [patch] ipv4: initialize arp_tbl rw lock

From: Christian Borntraeger
Date: Wed Apr 19 2006 - 06:45:55 EST


As spinlock debugging still does not work with the qeth driver I want to pick
up the discussion.

On Saturday 08 April 2006 12:12, Andrew Morton wrote:
> Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote:
[...]
> > -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>

What about putting this patch into mm and find out?
>
> 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().

I agree that the initcall order offers a lot of room for improvement (like
dependencies). Is anybody aware of any work into this direction?

--
Mit freundlichen Grüßen / Best Regards

Christian Borntraeger
Linux Software Engineer zSeries Linux & Virtualization



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/