no, and this is important. Loopback is initialized in fs_initcall which is called sufficiently before module_init.
I have checked the code and do not see initialization order mistakes right now. But, from now on, maintainer should pay attention for this unfortunate consequence :( Regards, Den Stephen Hemminger wrote: > On Fri, 24 Aug 2007 19:55:47 +0400 > "Denis V. Lunev" <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] wrote: >>> From: Daniel Lezcano <[EMAIL PROTECTED]> >>> >>> Doing this makes loopback.c a better example of how to do a >>> simple network device, and it removes the special case >>> single static allocation of a struct net_device, hopefully >>> making maintenance easier. >>> >>> Applies against net-2.6.24 >>> >>> Tested on i386, x86_64 >>> Compiled on ia64, sparc >> I think that a small note, that initialization order is changed will be >> good to record. After this, loopback MUST be allocated before any other >> networking subsystem initialization. And this is an important change. >> >> Regards, >> Den > > Yes, this code would break when other drivers are directly linked > in. > _______________________________________________ > Containers mailing list > [EMAIL PROTECTED] > https://lists.linux-foundation.org/mailman/listinfo/containers > > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > https://openvz.org/mailman/listinfo/devel > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html