linux.git/net/core/dev_mcast.c, branch v2.6.27

netdev: Do not use TX lock to protect address lists.

2008-07-15T07:15:08+00:00

Now that we have a specific lock to protect the network
device unicast and multicast lists, remove extraneous
grabs of the TX lock in cases where the code only needs
address list protection.

Signed-off-by: David S. Miller

netdev: Add netdev->addr_list_lock protection.

2008-07-15T07:13:44+00:00

Add netif_addr_{lock,unlock}{,_bh}() helpers.

Use them to protect operations that operate on or read
the network device unicast and multicast address lists.

Also use them in cases where the code simply wants to
block calls into the driver's ->set_rx_mode() and
->set_multicast_list() methods.

Signed-off-by: David S. Miller

[NET]: Use existing device list walker for /proc/dev_mcast.

2008-02-29T19:44:14+00:00

The seq_file_operations' dev_mc_seq_xxx callbacks do the same thing as
the dev_seq_xxx ones do, but skip the SEQ_START_TOKEN.

So use the existing exported dev_seq_xxx calls and handle the
SEQ_START_TOKEN in the dev_mc_seq_show().

Signed-off-by: Pavel Emelyanov 
Signed-off-by: David S. Miller

[VLAN]: set_rx_mode support for unicast address list

2008-02-01T03:28:24+00:00

Reuse the existing logic for multicast list synchronization for the
unicast address list. The core of dev_mc_sync/unsync are split out as
__dev_addr_sync/unsync and moved from dev_mcast.c to dev.c.  These are
then used to implement dev_unicast_sync/unsync as well.

I'm working on cleaning up Intel's FCoE stack, which generates new MAC
addresses from the fibre channel device id assigned by the fabric as
per the current draft specification in T11.  When using such a
protocol in a VLAN environment it would be nice to not always be
forced into promiscuous mode, assuming the underlying Ethernet driver
supports multiple unicast addresses as well.

Signed-off-by: Chris Leech 
Signed-off-by: Patrick McHardy

[NET]: Add some acquires/releases sparse annotations.

2008-01-28T23:00:31+00:00

Add __acquires() and __releases() annotations to suppress some sparse
warnings.

example of warnings :

net/ipv4/udp.c:1555:14: warning: context imbalance in 'udp_seq_start' - wrong
count at exit
net/ipv4/udp.c:1571:13: warning: context imbalance in 'udp_seq_stop' -
unexpected unlock

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller

[NET]: Consolidate net namespace related proc files creation.

2008-01-28T22:54:28+00:00

Signed-off-by: Denis V. Lunev 
Signed-off-by: Pavel Emelyanov 
Signed-off-by: David S. Miller

[NET]: Move unneeded data to initdata section.

2007-11-13T11:23:50+00:00

This patch reverts Eric's commit 2b008b0a8e96b726c603c5e1a5a7a509b5f61e35

It diets .text & .data section of the kernel if CONFIG_NET_NS is not set.
This is safe after list operations cleanup.

Signed-of-by: Denis V. Lunev 
Signed-off-by: David S. Miller

[NET]: Fix infinite loop in dev_mc_unsync().

2007-11-11T05:36:04+00:00

From: Joe Perches 

Based upon an initial patch and report by Luis R. Rodriguez.

Signed-off-by: David S. Miller

[NET]: Marking struct pernet_operations __net_initdata was inappropriate

2007-10-27T05:54:53+00:00

It is not safe to to place struct pernet_operations in a special section.
We need struct pernet_operations to last until we call unregister_pernet_subsys.
Which doesn't happen until module unload.

So marking struct pernet_operations is a disaster for modules in two ways.
- We discard it before we call the exit method it points to.
- Because I keep struct pernet_operations on a linked list discarding
  it for compiled in code removes elements in the middle of a linked
  list and does horrible things for linked insert.

So this looks safe assuming __exit_refok is not discarded
for modules.

Signed-off-by: Eric W. Biederman 
Signed-off-by: David S. Miller

[NETNS]: Move some code into __init section when CONFIG_NET_NS=n

2007-10-10T23:54:58+00:00

With the net namespaces many code leaved the __init section,
thus making the kernel occupy more memory than it did before.
Since we have a config option that prohibits the namespace
creation, the functions that initialize/finalize some netns
stuff are simply not needed and can be freed after the boot.

Currently, this is almost not noticeable, since few calls
are no longer in __init, but when the namespaces will be
merged it will be possible to free more code. I propose to
use the __net_init, __net_exit and __net_initdata "attributes"
for functions/variables that are not used if the CONFIG_NET_NS
is not set to save more space in memory.

The exiting functions cannot just reside in the __exit section,
as noticed by David, since the init section will have
references on it and the compilation will fail due to modpost
checks. These references can exist, since the init namespace
never dies and the exit callbacks are never called. So I
introduce the __exit_refok attribute just like it is already
done with the __init_refok.

Signed-off-by: Pavel Emelyanov 
Signed-off-by: David S. Miller