patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: zhichaox.zeng@intel.com
Cc: dev@dpdk.org, qiming.yang@intel.com, bruce.richardson@intel.com,
	hkalra@marvell.com, david.marchand@redhat.com,
	aconole@redhat.com, olivier.matz@6wind.com, thomas@monjalon.net,
	stable@dpdk.org
Subject: Re: [PATCH v3] lib/eal: fix segfaults due to thread exit order
Date: Mon, 30 May 2022 09:28:52 -0700	[thread overview]
Message-ID: <20220530092852.54638bdf@hermes.local> (raw)
In-Reply-To: <20220530134738.488602-1-zhichaox.zeng@intel.com>

On Mon, 30 May 2022 13:47:38 +0000
zhichaox.zeng@intel.com wrote:

> @@ -883,6 +896,8 @@ rte_eal_init(int argc, char **argv)
>  
>  	eal_mcfg_complete();
>  
> +	pthread_atfork(NULL, warn_parent, scratch_child);
> +
>  	return fctret;
>  }

There are lots of other cases where DPDK will die if you fork()
in a DPDK process then call DPDK functions in child. 

Not sure what the problem you are trying to solve is?

  parent reply	other threads:[~2022-05-30 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220523111642.10406-1-zhichaox.zeng@intel.com>
2022-05-30 13:47 ` zhichaox.zeng
2022-05-30 16:26   ` Stephen Hemminger
2022-05-30 16:28   ` Stephen Hemminger [this message]
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
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=20220530092852.54638bdf@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=olivier.matz@6wind.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).