From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: dsosnowski@nvidia.com, stable@dpdk.org,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH] test/debug: fix crash with mlx5 devices
Date: Thu, 2 Oct 2025 19:05:08 +0200 [thread overview]
Message-ID: <CAJFAV8x2xSmaPwUmrFMY=NN53JbG4WgEqJv3C7EJqhf5J-ugug@mail.gmail.com> (raw)
In-Reply-To: <20251002165546.523435-1-david.marchand@redhat.com>
On Thu, 2 Oct 2025 at 18:56, David Marchand <david.marchand@redhat.com> wrote:
>
> Running rte_exit() in a forked process means that shared memory will be
> released by the child process before the parent process does the same.
Another way of describing the issue is that the unit test code by
forking at rte_eal_init made it so two primary processes were
accessing the DPDK shared memory.
Nothing good can come from this...
--
David Marchand
prev parent reply other threads:[~2025-10-02 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:55 David Marchand
2025-10-02 17:05 ` David Marchand [this message]
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='CAJFAV8x2xSmaPwUmrFMY=NN53JbG4WgEqJv3C7EJqhf5J-ugug@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=roretzla@linux.microsoft.com \
--cc=stable@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).