DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yong Wang <yongwang@vmware.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: handle bad host framing
Date: Thu, 14 May 2020 17:15:09 +0100	[thread overview]
Message-ID: <d105257d-915d-5a6a-be31-965b93a04ad2@intel.com> (raw)
In-Reply-To: <260BA1B6-74AE-40D4-B415-E566C570D202@vmware.com>

On 5/13/2020 11:24 PM, Yong Wang wrote:
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Tuesday, May 12, 2020 at 1:40 PM
> To: Yong Wang <yongwang@vmware.com>
> Cc: "dev@dpdk.org" <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
> Subject: [PATCH] net/vmxnet3: handle bad host framing
> 
>     The VMXNet3 protocol has a start-of-packet (SOP) and end-of-packet (EOP)
>     marker. If there was a bug where mbuf arrived without SOP the code
>     that chains the mbuf would dereference a null pointer.
>     Also, record any mbuf's dropped in statistics.
> 
>     Although did the initial code no longer have access to VMware.
>     Compile tested only!
> 
>     Coverity issue: 124563
>     Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>     ---
> 
> <Acked-by> Yong Wang <yongwang@vmware.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-05-14 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 20:40 Stephen Hemminger
2020-05-13 22:24 ` Yong Wang
2020-05-14 16:15   ` Ferruh Yigit [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=d105257d-915d-5a6a-be31-965b93a04ad2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=yongwang@vmware.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).