DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>,
	anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] eal: fix use-after-free issue on thread creation
Date: Wed, 02 May 2018 17:26:18 +0200	[thread overview]
Message-ID: <2330312.QrEeuOKnyk@xps> (raw)
In-Reply-To: <20180502145622.5lka4i2hqehizij3@neon>

02/05/2018 16:56, Olivier Matz:
> On Wed, May 02, 2018 at 01:52:14PM +0000, Jianfeng Tan wrote:
> > After below commit, we encounter some strange issue:
> >   1) Dead lock as described here:
> >      http://dpdk.org/ml/archives/dev/2018-April/099806.html
> >   2) SIGSEGV issue when starting a testpmd in VM.
> > 
> > Considering below commit changes to use dynamic memory instead of
> > stack for memory barrier, we doubt it's caused by use-after-free.
> > 
> > Fixes: 3d09a6e26d8b ("eal: fix threads block on barrier")
> > 
> > Reported-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> > Reported-by: Lei Yao <lei.a.yao@intel.com>
> > Suggested-by: Stephen Hemminger <stephen@networkplumber.org>
> > Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> > Suggested-by: Olivier Matz <olivier.matz@6wind.com>
> 
> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
> 
> Thank you for fixing my stuff :)

Applied, thanks

      reply	other threads:[~2018-05-02 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02  9:59 [dpdk-dev] [PATCH] " Jianfeng Tan
2018-05-02 10:17 ` [dpdk-dev] [PATCH v2] " Jianfeng Tan
2018-05-02 11:24   ` Olivier Matz
2018-05-02 13:54     ` Tan, Jianfeng
2018-05-02 13:52 ` [dpdk-dev] [PATCH v3] " Jianfeng Tan
2018-05-02 14:56   ` Olivier Matz
2018-05-02 15:26     ` Thomas Monjalon [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=2330312.QrEeuOKnyk@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=olivier.matz@6wind.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).