Thread (8 messages) flat view 8 messages, 5 authors, 2016-06-13

Re: [PATCH net-next v2] bridge: Synchronize unicast filtering with FDB

From: David Miller <davem@davemloft.net>
Date: 2016-06-11 05:35:12
Also in: bridge

From: Toshiaki Makita <redacted>
Date: Mon,  6 Jun 2016 21:20:13 +0900
Patrick Schaaf reported that flooding due to a missing fdb entry of
the address of macvlan on the bridge device caused high CPU
consumption of an openvpn process behind a tap bridge port.
Adding an fdb entry of the macvlan address can suppress flooding
and avoid this problem.

This change makes bridge able to synchronize unicast filtering with
fdb automatically so admin do not need to manually add an fdb entry.
This effectively supports IFF_UNICAST_FLT in bridge, thus adding an
macvlan device would not place bridge into promiscuous mode as well.

v2:
- Test vlan with br_vlan_should_use() in br_fdb_sync_uc() as per
  Nikolay Aleksandrov.

Reported-by: Patrick Schaaf <redacted>
Signed-off-by: Toshiaki Makita <redacted>
I really need bridging experts to review and ACK/NACK this.

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help