From: Sergei Iashin <yashin.sergey@gmail.com>
To: Naga Harish K S V <s.v.naga.harish.k@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Jay Jayatheerthan <jay.jayatheerthan@intel.com>,
Ganapati Kundapura <ganapati.kundapura@intel.com>,
Weiguo Li <liweiguo@xencore.cn>
Cc: dev@dpdk.org, Sergei Iashin <yashin.sergey@gmail.com>,
liwg06@foxmail.com, stable@dpdk.org
Subject: [PATCH 1/2] eventdev: fix eth dev ID truncation in telemetry
Date: Wed, 4 Mar 2026 03:34:05 +0300 [thread overview]
Message-ID: <20260304003406.252929-2-yashin.sergey@gmail.com> (raw)
In-Reply-To: <20260304003406.252929-1-yashin.sergey@gmail.com>
eth_dev_id is declared as int in handle_rxa_get_queue_conf(),
handle_rxa_get_queue_stats(), handle_rxa_queue_stats_reset(), and
handle_rxa_instance_get(), but is implicitly narrowed to uint16_t when
passed to rte_eth_dev_is_valid_port() via
RTE_EVENT_ETH_RX_ADAPTER_PORTID_VALID_OR_GOTO_ERR_RET().
A value like 65535 + N passes validation as N, but is then used as-is as
an array index, causing out-of-bounds access and SIGSEGV.
To reproduce (requires telemetry enabled):
echo "/eventdev/rxa_queue_conf,0,65536,0" | \
socat - UNIX-CONNECT:/var/run/dpdk/vpp/dpdk_telemetry.v2,type=5
Result:
SIGSEGV at handle_rxa_get_queue_conf + 0x34a, faulting address 0x50
This patch changes eth_dev_id from int to uint16_t to avoid truncation.
Fixes: 74b034ff8172 ("eventdev/eth_rx: fix parameters parsing memory leak")
Cc: liwg06@foxmail.com
Cc: stable@dpdk.org
Signed-off-by: Sergei Iashin <yashin.sergey@gmail.com>
---
lib/eventdev/rte_event_eth_rx_adapter.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/lib/eventdev/rte_event_eth_rx_adapter.c b/lib/eventdev/rte_event_eth_rx_adapter.c
index d564e14b72..2183adce6f 100644
--- a/lib/eventdev/rte_event_eth_rx_adapter.c
+++ b/lib/eventdev/rte_event_eth_rx_adapter.c
@@ -3827,7 +3827,8 @@ handle_rxa_get_queue_conf(const char *cmd __rte_unused,
{
uint8_t rx_adapter_id;
uint16_t rx_queue_id;
- int eth_dev_id, ret = -1;
+ uint16_t eth_dev_id;
+ int ret = -1;
char *token, *l_params;
struct rte_event_eth_rx_adapter_queue_conf queue_conf;
@@ -3899,7 +3900,8 @@ handle_rxa_get_queue_stats(const char *cmd __rte_unused,
{
uint8_t rx_adapter_id;
uint16_t rx_queue_id;
- int eth_dev_id, ret = -1;
+ uint16_t eth_dev_id;
+ int ret = -1;
char *token, *l_params;
struct rte_event_eth_rx_adapter_queue_stats q_stats;
@@ -3970,7 +3972,8 @@ handle_rxa_queue_stats_reset(const char *cmd __rte_unused,
{
uint8_t rx_adapter_id;
uint16_t rx_queue_id;
- int eth_dev_id, ret = -1;
+ uint16_t eth_dev_id;
+ int ret = -1;
char *token, *l_params;
if (params == NULL || strlen(params) == 0 || !isdigit(*params))
@@ -4031,7 +4034,8 @@ handle_rxa_instance_get(const char *cmd __rte_unused,
{
uint8_t instance_id;
uint16_t rx_queue_id;
- int eth_dev_id, ret = -1;
+ uint16_t eth_dev_id;
+ int ret = -1;
char *token, *l_params;
if (params == NULL || strlen(params) == 0 || !isdigit(*params))
--
2.39.5
next prev parent reply other threads:[~2026-03-04 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 0:34 [PATCH 0/2] eventdev: fix eth dev ID truncation in telemetry Sergei Iashin
2026-03-04 0:34 ` Sergei Iashin [this message]
2026-03-04 0:34 ` [PATCH 2/2] mailmap: add Sergei Iashin Sergei Iashin
2026-03-24 17:34 ` Jerin Jacob
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=20260304003406.252929-2-yashin.sergey@gmail.com \
--to=yashin.sergey@gmail.com \
--cc=dev@dpdk.org \
--cc=ganapati.kundapura@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=liweiguo@xencore.cn \
--cc=liwg06@foxmail.com \
--cc=s.v.naga.harish.k@intel.com \
--cc=stable@dpdk.org \
/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