DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Haibo Zhang <zhanghaibo5@huawei.com>
Cc: dev@dpdk.org, zhoujingbin@huawei.com, zhangyuexi@huawei.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: check process type before reset dev data
Date: Thu, 12 Jan 2017 14:45:54 +0100	[thread overview]
Message-ID: <2621946.K4KTEV4MZ9@xps13> (raw)
In-Reply-To: <1484209998-21852-1-git-send-email-zhanghaibo5@huawei.com>

2017-01-12 16:33, Haibo Zhang:
> Overwrite dev date by no primary process would cause
> segment fault issue to primary proccess during receive pkt
> 
> Signed-off-by: Haibo Zhang <zhanghaibo5@huawei.com>

Thank you for the fix.
A similar one was proposed by Yuanhan:
	http://dpdk.org/ml/archives/dev/2017-January/054220.html

      reply	other threads:[~2017-01-12 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  8:33 Haibo Zhang
2017-01-12 13:45 ` 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=2621946.K4KTEV4MZ9@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=zhanghaibo5@huawei.com \
    --cc=zhangyuexi@huawei.com \
    --cc=zhoujingbin@huawei.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).