net/mlx5e: Remove redundant WARN when we cannot find neigh entry
It is possible for neigh entry not to exist if it was cleaned already. When we bring down an interface the neigh gets deleted but it could be that our listener for neigh event to clear the encap valid bit didn't start yet and the neigh update last used work is started first. In this scenario the encap entry has valid bit set but the neigh entry doesn't exist. Signed-off-by: Roi Dayan <roid@mellanox.com> Reviewed-by: Paul Blakey <paulb@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
This commit is contained in:
parent
3101d1fc6b
commit
c7f7ba8df8
|
@ -1032,10 +1032,8 @@ void mlx5e_tc_update_neigh_used_value(struct mlx5e_neigh_hash_entry *nhe)
|
|||
* dst ip pair
|
||||
*/
|
||||
n = neigh_lookup(tbl, &m_neigh->dst_ip, m_neigh->dev);
|
||||
if (!n) {
|
||||
WARN(1, "The neighbour already freed\n");
|
||||
if (!n)
|
||||
return;
|
||||
}
|
||||
|
||||
neigh_event_send(n, NULL);
|
||||
neigh_release(n);
|
||||
|
|
Loading…
Reference in a new issue