* struct net_device locking
@ 2011-12-29 18:24 michi1 at michaelblizek.twilightparadox.com
0 siblings, 0 replies; only message in thread
From: michi1 at michaelblizek.twilightparadox.com @ 2011-12-29 18:24 UTC (permalink / raw)
To: kernelnewbies
Hi!
I could not see any locking being done with "struct net_device" at all even
tough there are many read+write accesses to non-atomic variables. For example:
Changing mac addresses:
user space netlink socket call to set IFLA_ADDRESS
http://lxr.linux.no/linux+v3.1.6/net/core/rtnetlink.c#L1521
http://lxr.linux.no/linux+v3.1.6/net/core/rtnetlink.c#L1322
call to device, e.g. http://lxr.linux.no/linux+v3.1.6/drivers/net/e100.c#L2195
Sending an arp response:
http://lxr.linux.no/linux+v3.1.6/net/ipv4/arp.c#L859
Any ideas/pointers?
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-12-29 18:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-29 18:24 struct net_device locking michi1 at michaelblizek.twilightparadox.com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).