So how come I get the "RTNL: assertion failed at devinet.c(775):inetdev_event" when I call register_netdevice without rtnl_lock/unlock ? could it be a 2.4.0-test9 thing ? (haven't used test10 or 11 yet). and what about rmmod causing the panic when I use unregister_netdev or never completing the operation when I use unregister_netdevice ? does module_exit run inside rtnl_lock too ? Shmulik. -----Original Message----- From: Jeff Garzik [mailto:jgarzik@mandrakesoft.com] Sent: Thursday, November 09, 2000 7:37 PM To: Hen, Shmulik Cc: 'LNML'; 'LKML'; netdev@oss.sgi.com Subject: Re: catch 22 - porting net driver from 2.2 to 2.4 do_ioctl is inside rtnl_lock... Remember if you need to alter the rules, you can always queue work in the current context, and have a kernel thread handle the work. The nice thing about a kernel thread is that you start with a [almost] clean state, when it comes to locks. Jeff -- Jeff Garzik | Building 1024 | Would you like a Twinkie? MandrakeSoft | - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
