From: Olivier Matz <olivier.matz@6wind.com>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v3] eal: fix use-after-free issue on thread creation
Date: Wed, 2 May 2018 16:56:22 +0200 [thread overview]
Message-ID: <20180502145622.5lka4i2hqehizij3@neon> (raw)
In-Reply-To: <1525269134-103270-1-git-send-email-jianfeng.tan@intel.com>
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 :)
next prev parent reply other threads:[~2018-05-02 14:56 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 [this message]
2018-05-02 15:26 ` Thomas Monjalon
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=20180502145622.5lka4i2hqehizij3@neon \
--to=olivier.matz@6wind.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=thomas@monjalon.net \
/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).