diff options
| author | Dima Chumak <dchumak@nvidia.com> | 2021-06-30 14:56:32 +0300 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2021-08-26 15:15:41 -0700 |
| commit | 2f8b6161cca5fb34b0065e2eac8bb2b61b7bfe87 (patch) | |
| tree | 1b1f2f81d80e9480a5d3b4db1af917bc818436b3 /net/unix/sysctl_net_unix.c | |
| parent | 73367f05b25dbd064061aee780638564d15b01d1 (diff) | |
| download | linux-stable-2f8b6161cca5fb34b0065e2eac8bb2b61b7bfe87.tar.gz linux-stable-2f8b6161cca5fb34b0065e2eac8bb2b61b7bfe87.tar.bz2 linux-stable-2f8b6161cca5fb34b0065e2eac8bb2b61b7bfe87.zip | |
net/mlx5: Lag, fix multipath lag activation
When handling FIB_EVENT_ENTRY_REPLACE event for a new multipath route,
lag activation can be missed if a stale (struct lag_mp)->mfi pointer
exists, which was associated with an older multipath route that had been
removed.
Normally, when a route is removed, it triggers mlx5_lag_fib_event(),
which handles FIB_EVENT_ENTRY_DEL and clears mfi pointer. But, if
mlx5_lag_check_prereq() condition isn't met, for example when eswitch is
in legacy mode, the fib event is skipped and mfi pointer becomes stale.
Fix by resetting mfi pointer to NULL in mlx5_deactivate_lag().
Fixes: 8a66e4585979 ("net/mlx5: Change ownership model for lag")
Signed-off-by: Dima Chumak <dchumak@nvidia.com>
Reviewed-by: Roi Dayan <roid@nvidia.com>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions