Hi,

> -----Original Message-----
> From: Weiguo Li <liw...@foxmail.com>
> Sent: Saturday, November 4, 2023 6:08 AM
> To: Alexander Kozyrev <akozy...@nvidia.com>
> Cc: Slava Ovsiienko <viachesl...@nvidia.com>; dev@dpdk.org;
> sta...@dpdk.org; Weiguo Li <liwei...@xencore.cn>
> Subject: [PATCH] net/mlx5: fix the unlock mismatch issue
> 
> The 'need_lock' parameter controls whether the function acquires and
> releases the spinlock, but the first unlock operation occurs regardless of the
> 'need_lock' parameter.
> 
> To fix this issue, the spin unlock operation should be invoked within an 'if
> (need_lock)' block, ensuring that the function only unlocks the spinlock if it
> has previously been acquired.
> 
> Fixes: 48fbb0e93d06 ("net/mlx5: support flow meter mark indirect action
> with HWS")
> Cc: sta...@dpdk.org
> 
> Signed-off-by: Weiguo Li <liwei...@xencore.cn>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

Reply via email to