Re: catch 22 - porting net driver from 2.2 to 2.4

[Jeff Garzik <jgarzik@mandrakesoft.com>]

"Hen, Shmulik" wrote:
> 
> So how come I get the "RTNL: assertion failed at
> devinet.c(775):inetdev_event" when I call register_netdevice without
> rtnl_lock/unlock ?

Uh.  Don't do that.  You MUST call register_netdevice with rtnl_lock
held.


> 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 ?

module_exit does not run inside rtnl_lock.

Theoretically, if you call unregister_netdev from rmmon, it should grab
rtnl_lock and then complete the operation for you.  If that doesn't work
for you, it sounds like you are not setting up, or cleaning up,
something correctly.

Basically... it sounds like there are still bugs in your driver that
need working out :)

	Jeff


-- 
Jeff Garzik             |
Building 1024           | Would you like a Twinkie?
MandrakeSoft            |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/