From: Alexander Duyck <aduyck@mirantis.com>
To: netdev@vger.kernel.org, ogerlitz@mellanox.com,
davem@davemloft.net, alexander.duyck@gmail.com
Subject: [net PATCH 0/2] Fixes for tunnel checksum and segmentation offloads
Date: Mon, 02 May 2016 09:25:04 -0700 [thread overview]
Message-ID: <20160502161621.11701.9271.stgit@ahduyck-xeon-server> (raw)
This patch series is a subset of patches I had submitted for net-next. I
plan to drop these two patches from the v3 of "Fix Tunnel features and
enable GSO partial for several drivers" and I am instead submitting them
for net since these are truly fixes and likely will need to be backported
to stable branches.
This series addresses 2 specific issues. The first is that we could
request TSO on a v4 inner header while not supporting checksum offload of
the outer IPv6 header. The second is that we could request an IPv6 inner
checksum offload without validating that we could actually support an inner
IPv6 checksum offload.
---
Alexander Duyck (2):
net: Disable segmentation if checksumming is not supported
vxlan: Add checksum check to the features check function
include/linux/if_ether.h | 5 +++++
include/net/vxlan.h | 4 +++-
net/core/dev.c | 2 +-
3 files changed, 9 insertions(+), 2 deletions(-)
next reply other threads:[~2016-05-02 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 16:25 Alexander Duyck [this message]
2016-05-02 16:25 ` [net PATCH 1/2] net: Disable segmentation if checksumming is not supported Alexander Duyck
2016-05-02 16:33 ` Tom Herbert
2016-05-02 16:48 ` Alexander Duyck
2016-05-02 17:07 ` Tom Herbert
2016-05-02 17:20 ` Alexander Duyck
2016-05-02 16:25 ` [net PATCH 2/2] vxlan: Add checksum check to the features check function Alexander Duyck
2016-05-03 20:01 ` [net PATCH 0/2] Fixes for tunnel checksum and segmentation offloads David Miller
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=20160502161621.11701.9271.stgit@ahduyck-xeon-server \
--to=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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).