From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2] net/tap: fix close for partially configured port
Date: Fri, 27 Mar 2026 09:39:02 +0100 [thread overview]
Message-ID: <20260327083903.3394778-1-david.marchand@redhat.com> (raw)
In-Reply-To: <20260326124612.2580985-1-david.marchand@redhat.com>
In case no rxq has been set up (like when starting testpmd with no mempool
drivers), a crash happens in tap_dev_close:
Thread 1 "dpdk-testpmd" received signal SIGSEGV, Segmentation fault.
0x00007ffff7fad68b in tap_dev_close (dev=dev@entry=0x4c4a80
<rte_eth_devices@INTERNAL>) at ../drivers/net/tap/rte_eth_tap.c:1111
1111 struct rx_queue *rxq = dev->data->rx_queues[i];
(gdb) p dev->data->rx_queues
$4 = (void **) 0x0
Fixes: 23e2387b49a1 ("net/tap: allocate queue structures dynamically")
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
Changes since v1:
- as Stephen AI reported, [rt]x_queues array are sized against
dev->data->nb_[rt]x_queues, so the loop after the 23e2387b49a1 rework
can go out of bound. Since nb_rx_queues == nb_tx_queues with this
driver, simply check the number of configured rxq,
---
drivers/net/tap/rte_eth_tap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
index 64b359914b..a5d460a0b3 100644
--- a/drivers/net/tap/rte_eth_tap.c
+++ b/drivers/net/tap/rte_eth_tap.c
@@ -1107,7 +1107,7 @@ tap_dev_close(struct rte_eth_dev *dev)
}
#endif
- for (i = 0; i < RTE_PMD_TAP_MAX_QUEUES; i++) {
+ for (i = 0; i < dev->data->nb_rx_queues; i++) {
struct rx_queue *rxq = dev->data->rx_queues[i];
tap_queue_close(process_private, i);
--
2.53.0
next prev parent reply other threads:[~2026-03-27 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:46 [PATCH] net/tap: fix close for partially configured port David Marchand
2026-03-26 13:40 ` Bruce Richardson
2026-03-26 18:31 ` Stephen Hemminger
2026-03-27 8:29 ` David Marchand
2026-03-27 8:39 ` David Marchand [this message]
2026-03-27 15:37 ` [PATCH v2] " Stephen Hemminger
2026-03-27 16:22 ` Stephen Hemminger
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=20260327083903.3394778-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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