diff options
author | Vlad Buslov <vladbu@nvidia.com> | 2021-10-21 18:15:10 +0300 |
---|---|---|
committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-11-16 23:20:18 +0300 |
commit | 362980eada85b5ea691e5e0d9257a991aa7ade47 (patch) | |
tree | 522dd97c25971f2b857010b85426e98fcaf14b09 /include/linux/mlx5/eswitch.h | |
parent | cc4a9cc03faa6d8db1a6954bb536f2c1e63bdff6 (diff) | |
download | linux-362980eada85b5ea691e5e0d9257a991aa7ade47.tar.xz |
net/mlx5e: Wait for concurrent flow deletion during neigh/fib events
Function mlx5e_take_tmp_flow() skips flows with zero reference count. This
can cause syndrome 0x179e84 when the called from neigh or route update code
and the skipped flow is not removed from the hardware by the time
underlying encap/decap resource is deleted. Add new completion
'del_hw_done' that is completed when flow is unoffloaded. This is safe to
do because flow with reference count zero needs to be detached from
encap/decap entry before its memory is deallocated, which requires taking
the encap_tbl_lock mutex that is held by the event handlers code.
Fixes: 8914add2c9e5 ("net/mlx5e: Handle FIB events to update tunnel endpoint device")
Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
Reviewed-by: Roi Dayan <roid@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'include/linux/mlx5/eswitch.h')
0 files changed, 0 insertions, 0 deletions