linux-toradex.git/net/bridge/br_fdb.c, branch v3.4.48

bridge: BH already disabled in br_fdb_cleanup()

2012-01-17T15:17:32+00:00

br_fdb_cleanup() is run from timer interrupt, BH already masked.

Signed-off-by: Eric Dumazet 
CC: Stephen Hemminger 
CC: Štefan Gula 
Acked-by: Stephen Hemminger 
Signed-off-by: David S. Miller

net:bridge: use IS_ENABLED

2011-12-16T20:49:52+00:00

Use IS_ENABLED(CONFIG_FOO)
instead of defined(CONFIG_FOO) || defined (CONFIG_FOO_MODULE)

Signed-off-by: Igor Maravić 
Signed-off-by: David S. Miller

bridge: add local MAC address to forwarding table (v2)

2011-12-09T00:40:28+00:00

If user has configured a MAC address that is not one of the existing
ports of the bridge, then we need to add a special entry in the forwarding
table. This forwarding table entry has no outgoing port so it has to be
treated a little differently. The special entry is reported by the netlink
interface with ifindex of bridge, but ignored by the old interface since there
is no usable way to put it in the ABI.

Reported-by: Koki Sanagi 
Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: rearrange fdb notifications (v2)

2011-12-09T00:40:28+00:00

Pass bridge to fdb_notify so it can determine correct namespace based
on namespace of bridge rather than namespace of destination port.
Also makes next patch easier.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: refactor fdb_notify

2011-12-09T00:40:28+00:00

Move fdb_notify outside of fdb_create. This fixes the problem
that notification of local entries are not flagged correctly.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: add NTF_USE support

2011-11-14T05:41:54+00:00

More changes to the recent code to support control of forwarding
database via netlink.
   * Support NTF_USE like neighbour table
   * Validate state bits from application
   * Only send notifications (and change bits) if new entry is
     different.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: allow updating existing fdb entries

2011-10-03T16:17:33+00:00

Need to allow application to update existing fdb entries that already
exist. This makes bridge netlink neighbor API have same flags and
semantics as ip neighbor table.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

atomic: use

2011-07-26T23:49:47+00:00

This allows us to move duplicated code in 
(atomic_inc_not_zero() for now) to 

Signed-off-by: Arun Sharma 
Reviewed-by: Eric Dumazet 
Cc: Ingo Molnar 
Cc: David Miller 
Cc: Eric Dumazet 
Acked-by: Mike Frysinger 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6

2011-04-11T20:44:25+00:00

Conflicts:
	drivers/net/smsc911x.c

bridge: allow creating/deleting fdb entries via netlink

2011-04-05T00:22:28+00:00

Use RTM_NEWNEIGH and RTM_DELNEIGH to allow updating of entries
in bridge forwarding table. This allows manipulating static entries
which is not possible with existing tools.

Example (using bridge extensions to iproute2)
   # br fdb add 00:02:03:04:05:06 dev eth0

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller