From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1944] Crash due to corruption from data race in page prefault in alloc_seg()
Date: Wed, 13 May 2026 17:23:16 +0000 [thread overview]
Message-ID: <bug-1944-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1944
Bug ID: 1944
Summary: Crash due to corruption from data race in page
prefault in alloc_seg()
Product: DPDK
Version: 24.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: michal.sieron@nokia.com
Target Milestone: ---
Hi, recently we caught a data corruption seemingly caused by a page prefault in
`alloc_seg()` function from `lib/eal/linux/eal_memalloc.c`:
> *(volatile int *)addr = *(volatile int *)addr;
Internal investigation showed that `rte_eal_init()` from a secondary process
was indirectly calling this function, which in rare cases led to data
corruption.
In our case it resulted in a scheduler crash:
> EAL: PANIC in eth_event_queue_callback():
> Cannot restart RxQ(p:1,q:0) after max trying times 4, abort!
The issue is reported for v24.11, but I don't think it is tied to this specific
version and is a general problem since that prefault was added in v18.05.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-05-13 17:23 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-1944-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