linux-toradex.git/net/bridge/br_netlink.c, branch v3.14.49

bridge: Handle IFLA_ADDRESS correctly when creating bridge device

2014-05-31T20:20:35+00:00

[ Upstream commit 30313a3d5794472c3548d7288e306a5492030370 ]

When bridge device is created with IFLA_ADDRESS, we are not calling
br_stp_change_bridge_id(), which leads to incorrect local fdb
management and bridge id calculation, and prevents us from receiving
frames on the bridge device.

Reported-by: Tom Gundersen 
Signed-off-by: Toshiaki Makita 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

netlink: cleanup rntl_af_register

2014-01-02T04:42:19+00:00

The function __rtnl_af_register is never called outside this
code, and the return value is always 0.

Signed-off-by: David S. Miller

bridge: remove unnecessary condition judgment

2013-12-20T00:27:25+00:00

Because err is always negative, remove unnecessary condition
judgment.

Signed-off-by: Tan Xiaojun 
Signed-off-by: David S. Miller

net: more spelling fixes

2013-12-11T02:57:11+00:00

Various spelling fixes in networking stack

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

bridge: Don't use VID 0 and 4095 in vlan filtering

2013-10-18T20:02:52+00:00

IEEE 802.1Q says that:
- VID 0 shall not be configured as a PVID, or configured in any Filtering
Database entry.
- VID 4095 shall not be configured as a PVID, or transmitted in a tag
header. This VID value may be used to indicate a wildcard match for the VID
in management operations or Filtering Database entries.
(See IEEE 802.1Q-2011 6.9.1 and Table 9-2)

Don't accept adding these VIDs in the vlan_filtering implementation.

Signed-off-by: Toshiaki Makita 
Reviewed-by: Vlad Yasevich 
Acked-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: use br_port_get_rtnl within rtnl lock

2013-09-16T02:03:33+00:00

current br_port_get_rcu is problematic in bridging path
(NULL deref). Change these calls in netlink path first.

Signed-off-by: Hong Zhiguo 
Acked-by: Eric Dumazet 
Signed-off-by: David S. Miller

bridge: Use the correct bit length for bitmap functions in the VLAN code

2013-08-21T06:35:57+00:00

The VLAN code needs to know the length of the per-port VLAN bitmap to
perform its most basic operations (retrieving VLAN informations, removing
VLANs, forwarding database manipulation, etc). Unfortunately, in the
current implementation we are using a macro that indicates the bitmap
size in longs in places where the size in bits is expected, which in
some cases can cause what appear to be random failures.
Use the correct macro.

Signed-off-by: Toshiaki Makita 
Signed-off-by: David S. Miller

bridge: Add a flag to control unicast packet flood.

2013-06-11T09:04:32+00:00

Add a flag to control flood of unicast traffic.  By default, flood is
on and the bridge will flood unicast traffic if it doesn't know
the destination.  When the flag is turned off, unicast traffic
without an FDB will not be forwarded to the specified port.

Signed-off-by: Vlad Yasevich 
Reviewed-by: Michael S. Tsirkin 
Signed-off-by: David S. Miller

bridge: Add flag to control mac learning.

2013-06-11T09:04:32+00:00

Allow user to control whether mac learning is enabled on the port.
By default, mac learning is enabled.  Disabling mac learning will
cause new dynamic FDB entries to not be created for a particular port.

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

bridge: remove unused variable ifm

2013-03-28T18:41:19+00:00

Signed-off-by: Hong Zhiguo 
Acked-by: Stephen Hemminger 
Signed-off-by: David S. Miller