DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bing Zhao <bingz@nvidia.com>
To: <viacheslavo@nvidia.com>, <dev@dpdk.org>, <rasland@nvidia.com>
Cc: <orika@nvidia.com>, <dsosnowski@nvidia.com>,
	<suanmingm@nvidia.com>, <matan@nvidia.com>, <thomas@monjalon.net>
Subject: [PATCH] net/mlx5: fix decreasing the reference count of a Tx queue
Date: Thu, 3 Jul 2025 18:02:52 +0300	[thread overview]
Message-ID: <20250703150252.145065-1-bingz@nvidia.com> (raw)

When changing the order of the Tx queues startup, the depth of the
queue is compared. If not equal to the current big log2 value, next
queue will be checked and the current one will be skipped for the
next iteration.

The mlx5_txq_get() will increase the reference count number, and the
size check no match is not an error and the startup will continue but
not fall into the error roll-back label. The reference count should
be decreased by 1 to dereference the count, or else in the device
close stage, the queue cannot be released in the FW and the TIS, PD
will be leaked as well.

By calling the mlx5_txq_release() before continue will recover the
reference count to the initial state and solve the leak.

Fixes: 6f356d3840e6 ("net/mlx5: pass DevX object info in Tx queue start")

Signed-off-by: Bing Zhao <bingz@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
 drivers/net/mlx5/mlx5_trigger.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/drivers/net/mlx5/mlx5_trigger.c b/drivers/net/mlx5/mlx5_trigger.c
index 90287a1b75..6c6f228afd 100644
--- a/drivers/net/mlx5/mlx5_trigger.c
+++ b/drivers/net/mlx5/mlx5_trigger.c
@@ -61,8 +61,12 @@ mlx5_txq_start(struct rte_eth_dev *dev)
 			struct mlx5_txq_ctrl *txq_ctrl = mlx5_txq_get(dev, i);
 			struct mlx5_txq_data *txq_data = &txq_ctrl->txq;
 
-			if (!txq_ctrl || txq_data->elts_n != cnt)
+			if (!txq_ctrl)
+				continue;
+			if (txq_data->elts_n != cnt) {
+				mlx5_txq_release(dev, i);
 				continue;
+			}
 			if (!txq_ctrl->is_hairpin)
 				txq_alloc_elts(txq_ctrl);
 			MLX5_ASSERT(!txq_ctrl->obj);
-- 
2.34.1


                 reply	other threads:[~2025-07-03 15:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250703150252.145065-1-bingz@nvidia.com \
    --to=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).