lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 18 Nov 2011 17:48:49 +0530 From: Madhvapathi Sriram <sriram.madhvapathi@...il.com> To: netdev@...r.kernel.org Subject: Hi, In register_netdevice(), BUG_ON(dev->reg_state != NETREG_UNINITIALIZED) is used to check if the device that is being registered is indeed a new one. However, I see that this state is never moved to. It only happens when a netdevice is allocated (by default to 0 using kzalloc). So, the cycle register-->unregister-->register would fail since in the unregister_netdevice the state is only moved to NETREG_UNREGISTERED (at max to NETREG_RELEASED using free_netdev) So, I presume that to reinitialize a netdevice one has to free the netdevice, re allocate netdevice and only then re register. Wondering why unregister and reregister is not allowed, rather than having go through the free/alloc cycle - I am not an expert though. Thanks -Sriram -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists