From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>, zhichaox.zeng@intel.com
Cc: dev@dpdk.org, stable@dpdk.org, qiming.yang@intel.com,
stephen@networkplumber.org, mb@smartsharesystems.com,
Harman Kalra <hkalra@marvell.com>
Subject: Re: [PATCH v4] lib/eal: fix segfaults due to thread exit order
Date: Sun, 5 Oct 2025 18:39:56 +0200 [thread overview]
Message-ID: <CAJFAV8xS3_JMT1tpR=-MXL3zoLgWFg2kH6COxyoxLf8j8bL5eg@mail.gmail.com> (raw)
In-Reply-To: <Yr2V/yvgbWB4l6xW@bricha3-MOBL.ger.corp.intel.com>
On Thu, 30 Jun 2022 at 14:24, Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> On Wed, Jun 15, 2022 at 02:01:54PM +0800, zhichaox.zeng@intel.com wrote:
> > From: Zhichao Zeng <zhichaox.zeng@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@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
next prev parent reply other threads:[~2025-10-05 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220523111642.10406-1-zhichaox.zeng@intel.com>
2022-05-30 13:47 ` [PATCH v3] " zhichaox.zeng
2022-05-30 16:26 ` Stephen Hemminger
2022-05-30 16:28 ` Stephen Hemminger
2022-06-02 8:21 ` Zeng, ZhichaoX
2022-06-07 10:14 ` Zeng, ZhichaoX
2022-06-15 6:01 ` [PATCH v4] " zhichaox.zeng
2022-06-24 1:42 ` Zeng, ZhichaoX
2022-06-24 7:50 ` David Marchand
2022-06-30 10:38 ` Zeng, ZhichaoX
2022-06-30 12:24 ` Bruce Richardson
2025-10-05 16:39 ` David Marchand [this message]
2022-09-06 2:51 ` [PATCH v5] lib/eal: fix segfaults in exiting Zhichao Zeng
2022-09-06 15:03 ` Stephen Hemminger
2022-09-07 8:53 ` Zeng, ZhichaoX
2022-10-11 5:25 ` [PATCH v6] " Zhichao Zeng
2022-10-11 14:04 ` Stephen Hemminger
2022-10-19 1:51 ` Zeng, ZhichaoX
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='CAJFAV8xS3_JMT1tpR=-MXL3zoLgWFg2kH6COxyoxLf8j8bL5eg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=zhichaox.zeng@intel.com \
/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).