From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts
Date: Fri, 24 Nov 2017 03:39:36 +0900 (KST) [thread overview]
Message-ID: <20171124.033936.1934188261920003091.davem@davemloft.net> (raw)
In-Reply-To: <20171123144158.26111-1-aleksey.makarov@auriga.com>
From: Aleksey Makarov <aleksey.makarov@auriga.com>
Date: Thu, 23 Nov 2017 17:41:56 +0300
> From: Sunil Goutham <sgoutham@cavium.com>
>
> Don't offload IP header checksum to NIC.
>
> This fixes a previous patch which enabled checksum offloading
> for both IPv4 and IPv6 packets. So L3 checksum offload was
> getting enabled for IPv6 pkts. And HW is dropping these pkts
> as it assumes the pkt is IPv4 when IP csum offload is set
> in the SQ descriptor.
>
> Fixes: bbbb494fd005 ("net: thunderx: Enable TSO and checksum offloads for ipv6")
This fixes tag contains an invalid GIT SHA1-ID.
Please fix this up.
prev parent reply other threads:[~2017-11-23 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 14:41 [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts Aleksey Makarov
2017-11-23 18:10 ` Eric Dumazet
2017-11-23 18:39 ` David Miller [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=20171124.033936.1934188261920003091.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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).