diff options
author | Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp> | 2014-02-07 16:48:24 +0900 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-02-10 14:34:34 -0800 |
commit | a778e6d1a51faaafa6a3a3cef9bee11c3bd47f9f (patch) | |
tree | 9506ceeb6f8a4cdd7ad18b507d6130d240cb8471 /firmware/ttusb-budget | |
parent | 960b589f86c74ce582922fcb996103271081f4de (diff) | |
download | linux-a778e6d1a51faaafa6a3a3cef9bee11c3bd47f9f.tar.gz linux-a778e6d1a51faaafa6a3a3cef9bee11c3bd47f9f.tar.bz2 linux-a778e6d1a51faaafa6a3a3cef9bee11c3bd47f9f.zip |
bridge: Properly check if local fdb entry can be deleted in br_fdb_delete_by_port
br_fdb_delete_by_port() doesn't care about vlan and mac address of the
bridge device.
As the check is almost the same as mac address changing, slightly modify
fdb_delete_local() and use it.
Note that we can always set added_by_user to 0 in fdb_delete_local() because
- br_fdb_delete_by_port() calls fdb_delete_local() for local entries
regardless of its added_by_user. In this case, we have to check if another
port has the same address and vlan, and if found, we have to create the
entry (by changing dst). This is kernel-added entry, not user-added.
- br_fdb_changeaddr() doesn't call fdb_delete_local() for user-added entry.
Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Acked-by: Vlad Yasevich <vyasevic@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'firmware/ttusb-budget')
0 files changed, 0 insertions, 0 deletions