From: Erez Shitrit <ere...@nvidia.com>
While matcher is being connect/disconnect in shared gvmi flow we set the
first ft in the table to point on the first matcher,
The FW is increasing the refcount on the first matcher RTC because of
that no matcher if it is the same RTC that was set before, and when we
will try to release that RTC we will get the following syndrome:
0xaa0093 - destroy_rtc_object: rtc in use or doesn't exist.
In order to resolve that we clean the current pointed RTC from that ft
and only after that setting it to the new RTC value.
Signed-off-by: Erez Shitrit <ere...@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viachesl...@nvidia.com>
---
drivers/net/mlx5/hws/mlx5dr_matcher.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/drivers/net/mlx5/hws/mlx5dr_matcher.c
b/drivers/net/mlx5/hws/mlx5dr_matcher.c
index 5508cfe230..6af493d87a 100644
--- a/drivers/net/mlx5/hws/mlx5dr_matcher.c
+++ b/drivers/net/mlx5/hws/mlx5dr_matcher.c
@@ -334,6 +334,24 @@ static int mlx5dr_matcher_disconnect(struct mlx5dr_matcher
*matcher)
return ret;
}
+ if (!next) {
+ /* ft no longer points to any RTC, drop refcount */
+ ret = mlx5dr_matcher_free_rtc_pointing(tbl->ctx,
+ tbl->fw_ft_type,
+ tbl->type,
+ prev_ft);
+ if (ret) {
+ DR_LOG(ERR, "Failed to reset last RTC refcount");
+ return ret;
+ }
+ }
+
+ ret = mlx5dr_matcher_shared_update_local_ft(tbl);
+ if (ret) {
+ DR_LOG(ERR, "Failed to update local_ft in shared table");
+ return ret;
+ }
+
return 0;
}
--
2.18.1
