If a meter's profile is changed after meter disabled, there's an issue
that will fail when deleting the old profile.

This patch fixes this by adding the correct process to decrease the old
profile's reference count when changing profile.

Fixes: 63ffeb2ff2 ("net/mlx5: support meter profile update")
Cc: sta...@dpdk.org

Signed-off-by: Shun Hao <sh...@nvidia.com>
Acked-by: Matan Azrad <ma...@mellanox.com>
---
 drivers/net/mlx5/mlx5_flow_meter.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/net/mlx5/mlx5_flow_meter.c 
b/drivers/net/mlx5/mlx5_flow_meter.c
index 7c0d84907a..d4aafe4eea 100644
--- a/drivers/net/mlx5/mlx5_flow_meter.c
+++ b/drivers/net/mlx5/mlx5_flow_meter.c
@@ -1656,7 +1656,7 @@ mlx5_flow_meter_profile_update(struct rte_eth_dev *dev,
        fm->profile = fmp;
        /* Update meter params in HW (if not disabled). */
        if (fm->active_state == MLX5_FLOW_METER_DISABLE)
-               return 0;
+               goto dec_ref_cnt;
        ret = mlx5_flow_meter_action_modify(priv, fm, &fm->profile->srtcm_prm,
                                              modify_bits, fm->active_state, 1);
        if (ret) {
@@ -1666,6 +1666,7 @@ mlx5_flow_meter_profile_update(struct rte_eth_dev *dev,
                                          NULL, "Failed to update meter"
                                          " parameters in hardware.");
        }
+dec_ref_cnt:
        old_fmp->ref_cnt--;
        fmp->ref_cnt++;
        return 0;
-- 
2.20.0

Reply via email to