From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1783] crash in rollback_expand_heap
Date: Fri, 29 Aug 2025 16:24:21 +0000 [thread overview]
Message-ID: <bug-1783-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1783
Bug ID: 1783
Summary: crash in rollback_expand_heap
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,
We are observing a crash in rollback_expand_heap(). Below is the backtrace
Program terminated with signal 11, Segmentation fault.
#0 0x000000000088ebc4 in malloc_elem_init (elem=elem@entry=0x310024a00000,
heap=0x30ffffffdac0, msl=0x30ffffff9090,
size=18446744073709510528, orig_elem=0x310024600000, orig_size=2097152,
dirty=false)
at ../esbc_gnu_src/lib/eal/common/malloc_elem.c:128
128 ../esbc_gnu_src/lib/eal/common/malloc_elem.c: No such file or
directory.
(gdb) bt
#0 0x000000000088ebc4 in malloc_elem_init (elem=elem@entry=0x310024a00000,
heap=0x30ffffffdac0, msl=0x30ffffff9090,
size=18446744073709510528, orig_elem=0x310024600000, orig_size=2097152,
dirty=false)
at ../esbc_gnu_src/lib/eal/common/malloc_elem.c:128
#1 0x000000000088ec6b in split_elem (elem=elem@entry=0x310024600000,
split_pt=split_pt@entry=0x310024a00000)
at ../esbc_gnu_src/lib/eal/common/malloc_elem.c:297
#2 0x000000000088f2db in malloc_elem_hide_region () at
../esbc_gnu_src/lib/eal/common/malloc_elem.c:627
#3 0x000000000088fb6b in rollback_expand_heap (ms=0x2a5e278, n_segs=1,
elem=0x310024600000, map_addr=0x310024800000,
map_len=2097152) at ../esbc_gnu_src/lib/eal/common/malloc_heap.c:285
#4 0x000000000089145b in handle_sync_response () at
../esbc_gnu_src/lib/eal/common/malloc_mp.c:506
#5 0x0000000000888110 in trigger_async_action (sr=0x13c7e400) at
../esbc_gnu_src/lib/eal/common/eal_common_proc.c:504
#6 0x0000000000898763 in eal_alarm_callback (arg=<optimized out>) at
../esbc_gnu_src/lib/eal/linux/eal_alarm.c:105
#7 0x000000000089ad5c in eal_intr_process_interrupts (nfds=<optimized out>,
events=<optimized out>)
at ../esbc_gnu_src/lib/eal/linux/eal_interrupts.c:1017
#8 eal_intr_handle_interrupts (totalfds=<optimized out>, pfd=18) at
../esbc_gnu_src/lib/eal/linux/eal_interrupts.c:1091
#9 eal_intr_thread_main () at
../esbc_gnu_src/lib/eal/linux/eal_interrupts.c:1163
can you let us know if this is an know issue?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4426 bytes --]
reply other threads:[~2025-08-29 16:24 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-1783-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).