From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1273] eth_memif_rx segfault when burst size is greater than 32
Date: Mon, 14 Aug 2023 15:26:03 +0000 [thread overview]
Message-ID: <bug-1273-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1273
Bug ID: 1273
Summary: eth_memif_rx segfault when burst size is greater than
32
Product: DPDK
Version: 23.03
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: sunnylandh@gmail.com
Target Milestone: ---
When rte_eth_rx_burst() is called on an memif device with a burst size greater
than 32, there's a segfault in eth_memif_rx() function.
Thread 1 "x" received signal SIGSEGV, Segmentation fault.
0x00007ffff7a116d1 in eth_memif_rx (queue=0x1b73051c0, bufs=0x7fffffffd320,
nb_pkts=<optimized out>) at ../drivers/net/memif/rte_eth_memif.c:360
360 mbuf = mbuf_head;
(gdb) bt
#0 0x00007ffff7a116d1 in eth_memif_rx (queue=0x1b73051c0,
bufs=0x7fffffffd320, nb_pkts=<optimized out>) at
../drivers/net/memif/rte_eth_memif.c:360
#1 0x000055555555554e in rte_eth_rx_burst (nb_pkts=<optimized out>,
rx_pkts=0x7fffffffd220, queue_id=0, port_id=0) at
/usr/local/include/rte_ethdev.h:5918
#2 rxloop (queue=0, mp=<optimized out>, burstSize=<optimized out>, port=0)
at x.c:51
#3 main (argc=<optimized out>, argv=<optimized out>) at x.c:103
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3376 bytes --]
next reply other threads:[~2023-08-14 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 15:26 bugzilla [this message]
2023-09-06 14:20 ` bugzilla
2023-09-06 14:22 ` bugzilla
2023-10-11 16:46 ` bugzilla
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=bug-1273-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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;
as well as URLs for NNTP newsgroup(s).