[PATCH v4] lib/eal: fix segfaults due to thread exit order

David Marchand david.marchand at redhat.com
Sun Oct 5 18:39:56 CEST 2025


On Thu, 30 Jun 2022 at 14:24, Bruce Richardson
<bruce.richardson at intel.com> wrote:
>
> On Wed, Jun 15, 2022 at 02:01:54PM +0800, zhichaox.zeng at intel.com wrote:
> > From: Zhichao Zeng <zhichaox.zeng at intel.com>
> >
> > The eal-intr-thread is not closed before memory cleanup in the
> > process of exiting. There is a small probability that when the
> > eal-intr-thread is about to use some pointers, the memory were
> > just cleaned, which cause the segment fault error caught by ASan.
> >
> > This patch close the eal-intr-thread before memory cleanup when
> > exiting to avoid segment fault. And add some atomic operations
> > to avoid executing rte_eal_cleanup in the child process spawned
> > by fork() in some test cases, e.g. debug_autotest of dpdk-test.
> >
> > Cc: stable at dpdk.org

I am not sure if the issue this patch tried to fix still exists.
However, the problem around usage of fork() in the debug_autotest unit
test is probably addressed with 2b403dd8fb37 ("test/debug: fix crash
with mlx5 devices").


-- 
David Marchand



More information about the stable mailing list