From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Stringer <joestringer@nicira.com>
Cc: netdev@vger.kernel.org, matthew.vick@intel.com,
linux.nics@intel.com, therbert@google.com, gerlitz.or@gmail.com,
alexander.duyck@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 net 1/2] fm10k: Check tunnel header length in encap offload
Date: Thu, 13 Nov 2014 15:41:23 -0800 [thread overview]
Message-ID: <1415922083.2454.33.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1415921801-10452-1-git-send-email-joestringer@nicira.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Thu, 2014-11-13 at 15:36 -0800, Joe Stringer wrote:
> fm10k supports up to 184 bytes of inner+outer headers. Add an initial
> check to fail encap offload if these are too large.
>
> Signed-off-by: Joe Stringer <joestringer@nicira.com>
> ---
> Matthew, I didn't see the equivalent patch on netdev so I went ahead
> and
> created it. If I've missed this somewhere, then please disregard.
>
> v2: First post.
> ---
> drivers/net/ethernet/intel/fm10k/fm10k_main.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Thanks Joe, I will add your patch to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-13 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 23:36 [PATCHv2 net 1/2] fm10k: Check tunnel header length in encap offload Joe Stringer
2014-11-13 23:36 ` [PATCHv2 net 2/2] fm10k: Implement ndo_gso_check() Joe Stringer
2014-11-13 23:41 ` Jeff Kirsher
2014-11-13 23:52 ` Joe Stringer
2014-11-14 0:12 ` Jeff Kirsher
2014-11-14 0:29 ` Joe Stringer
2014-11-13 23:41 ` Jeff Kirsher [this message]
2014-11-14 0:41 ` [PATCHv2 net 1/2] fm10k: Check tunnel header length in encap offload Vick, Matthew
2014-11-14 0:54 ` Joe Stringer
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=1415922083.2454.33.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=gerlitz.or@gmail.com \
--cc=joestringer@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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