patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>, stable@dpdk.org
Cc: nd@arm.com, Jia He <justin.he@arm.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [PATCH 21.11] test/mbuf: fix crash in a forked process
Date: Tue, 25 Jul 2023 10:17:13 +0100	[thread overview]
Message-ID: <139c1f20-437d-ff0c-1b2a-f6c9cc5dd0b2@redhat.com> (raw)
In-Reply-To: <20230725085324.53061-1-ruifeng.wang@arm.com>

On 25/07/2023 09:53, Ruifeng Wang wrote:
> [ upstream commit b6c419dde10e9f5dec7a02098c48060a7493420c ]
> 
> test/mbuf: fix crash in a forked process
> 
> Access of any memory in the hugepage shared file-backed area will trigger
> an unexpected forked child process segment fault. The root cause is DPDK
> doesn't support fork model [1] (calling rte_eal_init() before fork()).
> Forked child process can't be treated as a secondary process.
> 
> Hence fix it by avoiding fork and doing verification in the main process.
> 
> [1]https://mails.dpdk.org/archives/dev/2018-July/108106.html
> 
> Fixes: af75078fece3 ("first public release")
> 
> Signed-off-by: Jia He<justin.he@arm.com>
> Signed-off-by: Ruifeng Wang<ruifeng.wang@arm.com>
> Acked-by: Anatoly Burakov<anatoly.burakov@intel.com>
> ---

Thanks for the backport. Queued, and will push to 21.11 dpdk.org branch 
in coming days.


      reply	other threads:[~2023-07-25  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  8:53 Ruifeng Wang
2023-07-25  9:17 ` Kevin Traynor [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=139c1f20-437d-ff0c-1b2a-f6c9cc5dd0b2@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=justin.he@arm.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.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).