patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, dsosnowski@nvidia.com, stable@dpdk.org,
	 Tyler Retzlaff <roretzla@linux.microsoft.com>,
	 Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] test/debug: fix crash with mlx5 devices
Date: Sun, 5 Oct 2025 18:29:00 +0200	[thread overview]
Message-ID: <CAJFAV8yQ0RHBPfVYMYfEAjmc+gmw8k9Kje8n8PHH=5gY+58=Ow@mail.gmail.com> (raw)
In-Reply-To: <20251003065101.617467-1-david.marchand@redhat.com>

On Fri, 3 Oct 2025 at 08:51, 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.
> This issue has been seen recently when some GHA virtual machine (with
> some mlx5 devices) runs the debug_autotest unit test.
>
> Instead, run rte_panic() and rte_exit() from a new DPDK process spawned
> like for other recursive unit tests.
>
> Bugzilla ID: 1796
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Applied, thanks for the reviews.


-- 
David Marchand


      parent reply	other threads:[~2025-10-05 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 16:55 [PATCH] " David Marchand
2025-10-02 17:05 ` David Marchand
2025-10-03  6:51 ` [PATCH v2] " David Marchand
2025-10-03  7:32   ` Bruce Richardson
2025-10-03 17:54   ` Dariusz Sosnowski
2025-10-05 16:29   ` 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='CAJFAV8yQ0RHBPfVYMYfEAjmc+gmw8k9Kje8n8PHH=5gY+58=Ow@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.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).