diff options
author | 2021-01-06 11:51:31 +0200 | |
---|---|---|
committer | 2021-01-07 15:34:45 -0800 | |
commit | 2fd186501b1cff155cc4a755c210793cfc0dffb5 (patch) | |
tree | 81e697fab85392b18503e1ad935fd18904aa3395 /net/core/sock_map.c | |
parent | net: bridge: notify switchdev of disappearance of old FDB entry upon migration (diff) | |
download | wireguard-linux-2fd186501b1cff155cc4a755c210793cfc0dffb5.tar.xz wireguard-linux-2fd186501b1cff155cc4a755c210793cfc0dffb5.zip |
net: dsa: be louder when a non-legacy FDB operation fails
The dev_close() call was added in commit c9eb3e0f8701 ("net: dsa: Add
support for learning FDB through notification") "to indicate inconsistent
situation" when we could not delete an FDB entry from the port.
bridge fdb del d8:58:d7:00:ca:6d dev swp0 self master
It is a bit drastic and at the same time not helpful if the above fails
to only print with netdev_dbg log level, but on the other hand to bring
the interface down.
So increase the verbosity of the error message, and drop dev_close().
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/core/sock_map.c')
0 files changed, 0 insertions, 0 deletions