From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/enic: fix possible Rx corruption
Date: Fri, 22 Jul 2016 00:46:47 +0200 [thread overview]
Message-ID: <2741378.dfrx3epoUB@xps13> (raw)
In-Reply-To: <1468968163-31556-1-git-send-email-johndale@cisco.com>
2016-07-19 15:42, John Daley:
> Initialize the mbuf data offset to RTE_PKTMBUF_HEADROOM as the
> enic takes ownership of them. If allocated mbufs had some offset
> other than RTE_PKTMBUF_HEADROOM, the application would read mbuf
> data starting at the wrong place and misinterpret the packet.
>
> Fixes: 856d7ba7ed22 ("net/enic: support scattered Rx")
>
> Reviewed-by: Nelson Escobar <neescoba@cisco.com>
> Signed-off-by: John Daley <johndale@cisco.com>
Applied, thanks
prev parent reply other threads:[~2016-07-21 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 22:42 John Daley
2016-07-21 22:46 ` 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=2741378.dfrx3epoUB@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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).