From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1784] crash is seen while reserving the memory in rte_memzone_reserve
Date: Mon, 01 Sep 2025 07:39:03 +0000 [thread overview]
Message-ID: <bug-1784-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2999 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1784
Bug ID: 1784
Summary: crash is seen while reserving the memory in
rte_memzone_reserve
Product: DPDK
Version: 24.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: malve.vinay.kumar@oracle.com
Target Milestone: ---
Hi,
While the application is reserving the memory for the stats table, we see a
crash.
Below is the BT
Program terminated with signal 11, Segmentation fault.
#0 0x0000000002b35f81 in elem_start_pt (elem=elem@entry=0x311032000000,
size=size@entry=34754368, align=align@entry=64,
bound=bound@entry=0, contig=contig@entry=false) at
../esbc_gnu_src/lib/eal/common/malloc_elem.c:222
222 ../esbc_gnu_src/lib/eal/common/malloc_elem.c: No such file or
directory.
(gdb) bt
#0 0x0000000002b35f81 in elem_start_pt (elem=elem@entry=0x311032000000,
size=size@entry=34754368, align=align@entry=64,
bound=bound@entry=0, contig=contig@entry=false) at
../esbc_gnu_src/lib/eal/common/malloc_elem.c:222
#1 0x0000000002b363cd in malloc_elem_can_hold (elem=elem@entry=0x311032000000,
size=size@entry=34754368,
align=align@entry=64, bound=bound@entry=0, contig=contig@entry=false) at
../esbc_gnu_src/lib/eal/common/malloc_elem.c:283
#2 0x0000000002b36c7b in find_suitable_element
(heap=heap@entry=0x30ffffffdb80, size=size@entry=34754368,
flags=flags@entry=0, align=align@entry=64, bound=bound@entry=0,
contig=contig@entry=false)
at ../esbc_gnu_src/lib/eal/common/malloc_heap.c:160
#3 0x0000000002b36d2f in heap_alloc (heap=heap@entry=0x30ffffffdb80,
size=size@entry=34754368, flags=flags@entry=0,
align=align@entry=64, bound=bound@entry=0, contig=contig@entry=false) at
../esbc_gnu_src/lib/eal/common/malloc_heap.c:244
#4 0x0000000002b37950 in malloc_heap_alloc_on_heap_id () at
../esbc_gnu_src/lib/eal/common/malloc_heap.c:680
#5 0x0000000002b37abb in malloc_heap_alloc (size=size@entry=34754368,
socket_arg=<optimized out>, flags=flags@entry=0,
align=align@entry=64, bound=bound@entry=0, contig=<optimized out>) at
../esbc_gnu_src/lib/eal/common/malloc_heap.c:755
#6 0x0000000002b2bef2 in memzone_reserve_aligned_thread_unsafe (bound=0,
align=64, flags=0, socket_id=<optimized out>,
len=34754368, name=0x4320efc4 "UsdpStatsTable/21") at
../esbc_gnu_src/lib/eal/common/eal_common_memzone.c:205
#7 rte_memzone_reserve_thread_safe () at
../esbc_gnu_src/lib/eal/common/eal_common_memzone.c:256
#8 0x0000000002b2c15e in rte_memzone_reserve (name=name@entry=0x4320efc4
"UsdpStatsTable/21", len=len@entry=34754352,
socket_id=<optimized out>, flags=flags@entry=0) at
../esbc_gnu_src/lib/eal/common/eal_common_memzone.c:300
Thanks,
Vinay.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5049 bytes --]
reply other threads:[~2025-09-01 7:39 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=bug-1784-3@https.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).