DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [DPDK/core Bug 1944] Crash due to corruption from data race in page prefault in alloc_seg()
@ 2026-05-13 17:23 bugzilla
  0 siblings, 0 replies; only message in thread
From: bugzilla @ 2026-05-13 17:23 UTC (permalink / raw)
  To: dev

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-05-13 17:23 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-13 17:23 [DPDK/core Bug 1944] Crash due to corruption from data race in page prefault in alloc_seg() bugzilla

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox