diff options
| author | Patrisious Haddad <phaddad@nvidia.com> | 2025-02-20 08:47:10 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-03-07 18:25:28 +0100 |
| commit | 6782ba62a654d24e6264a4d4aa52e48dc8bfe3d5 (patch) | |
| tree | a637755d769a4e25ddaa9a4d114e017c42db93e7 /scripts/stackusage | |
| parent | 465a8143238b5339391919fbf553aa27395bea08 (diff) | |
| download | linux-6782ba62a654d24e6264a4d4aa52e48dc8bfe3d5.tar.gz linux-6782ba62a654d24e6264a4d4aa52e48dc8bfe3d5.tar.bz2 linux-6782ba62a654d24e6264a4d4aa52e48dc8bfe3d5.zip | |
RDMA/mlx5: Fix bind QP error cleanup flow
[ Upstream commit e1a0bdbdfdf08428f0ede5ae49c7f4139ac73ef5 ]
When there is a failure during bind QP, the cleanup flow destroys the
counter regardless if it is the one that created it or not, which is
problematic since if it isn't the one that created it, that counter could
still be in use.
Fix that by destroying the counter only if it was created during this call.
Fixes: 45842fc627c7 ("IB/mlx5: Support statistic q counter configuration")
Signed-off-by: Patrisious Haddad <phaddad@nvidia.com>
Reviewed-by: Mark Zhang <markzhang@nvidia.com>
Link: https://patch.msgid.link/25dfefddb0ebefa668c32e06a94d84e3216257cf.1740033937.git.leon@kernel.org
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Signed-off-by: Leon Romanovsky <leon@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions