From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Jie Hai <haijie1@huawei.com>,
dev@dpdk.org, thomas@monjalon.net, ferruh.yigit@amd.com,
Keith Wiles <keith.wiles@intel.com>,
Billy McFall <bmcfall@redhat.com>
Cc: lihuisong@huawei.com, fengchengwen@huawei.com
Subject: Re: [PATCH 1/4] ethdev: verify queue ID when Tx done cleanup
Date: Thu, 5 Sep 2024 10:33:16 +0300 [thread overview]
Message-ID: <20681877-7c2a-4b54-bf32-0de7779df55c@oktetlabs.ru> (raw)
In-Reply-To: <20240905064638.17980-2-haijie1@huawei.com>
On 9/5/24 09:46, Jie Hai wrote:
> From: Chengwen Feng <fengchengwen@huawei.com>
>
> Verify queue_id for rte_eth_tx_done_cleanup API.
If I'm not mistaken the function is considered data path API (fast).
If so, it should not validate it's parameters as in rte_eth_tx_burst().
It may be done under RTE_ETHDEV_DEBUG_TX only.
May be documentation should be fixed to highlight it.
And yes, current implementation looks inconsistent from this point of
view since port_id and presence of callback are checked.
Anyway motivation in the patch description is insufficient.
>
> Fixes: 44a718c457b5 ("ethdev: add API to free consumed buffers in Tx ring")
> Cc: stable@dpdk.org
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
> lib/ethdev/rte_ethdev.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> index f1c658f49e80..998deb5ab101 100644
> --- a/lib/ethdev/rte_ethdev.c
> +++ b/lib/ethdev/rte_ethdev.c
> @@ -2823,6 +2823,10 @@ rte_eth_tx_done_cleanup(uint16_t port_id, uint16_t queue_id, uint32_t free_cnt)
> RTE_ETH_VALID_PORTID_OR_ERR_RET(port_id, -ENODEV);
> dev = &rte_eth_devices[port_id];
>
> + ret = eth_dev_validate_tx_queue(dev, queue_id);
> + if (ret != 0)
> + return ret;
> +
> if (*dev->dev_ops->tx_done_cleanup == NULL)
> return -ENOTSUP;
>
next prev parent reply other threads:[~2024-09-05 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:46 [PATCH 0/4] clean code for dmadev and hns3 Jie Hai
2024-09-05 6:46 ` [PATCH 1/4] ethdev: verify queue ID when Tx done cleanup Jie Hai
2024-09-05 7:33 ` Andrew Rybchenko [this message]
2024-09-05 6:46 ` [PATCH 2/4] net/hns3: verify reset type from firmware Jie Hai
2024-09-05 6:46 ` [PATCH 3/4] dmadev: fix potential null pointer access Jie Hai
2024-09-05 6:46 ` [PATCH 4/4] dmadev: clean code for verify parameter Jie Hai
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=20681877-7c2a-4b54-bf32-0de7779df55c@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=bmcfall@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=keith.wiles@intel.com \
--cc=lihuisong@huawei.com \
--cc=thomas@monjalon.net \
/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).