patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <dsosnowski@nvidia.com>, <stable@dpdk.org>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH v2] test/debug: fix crash with mlx5 devices
Date: Fri, 3 Oct 2025 08:32:57 +0100	[thread overview]
Message-ID: <aN98KbxZZwLVgh2X@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251003065101.617467-1-david.marchand@redhat.com>

On Fri, Oct 03, 2025 at 08:51:01AM +0200, David Marchand 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>
> ---
> Changes since v1:
> - revert last minute cosmetic change that broke the fix... iow pass
>   the name of the function to run, instead of __func__,
> 
> ---
>  app/test/process.h    |  2 +-
>  app/test/test.c       |  2 +
>  app/test/test.h       |  2 +
>  app/test/test_debug.c | 92 ++++++++++++++++++++++++++++++-------------
>  4 files changed, 69 insertions(+), 29 deletions(-)
> 

Fix seems reasonable.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>


      reply	other threads:[~2025-10-03  7:33 UTC|newest]

Thread overview: 4+ 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 [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=aN98KbxZZwLVgh2X@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=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).