From: Steffen Klassert <steffen.klassert@secunet.com>
To: Yossi Kuperman <yossiku@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Yevgeny Kliteynik <kliteyn@mellanox.com>,
Boris Pismenny <borisp@mellanox.com>,
Ilan Tayari <ilant@mellanox.com>
Subject: Re: [PATCH net 1/2] xfrm6: Fix IPv6 payload_len in xfrm6_transport_finish
Date: Thu, 22 Jun 2017 09:15:50 +0200 [thread overview]
Message-ID: <20170622071550.GT2631@secunet.com> (raw)
In-Reply-To: <AM4PR0501MB227460BDE5F2C9A370E13B80C4DA0@AM4PR0501MB2274.eurprd05.prod.outlook.com>
On Wed, Jun 21, 2017 at 08:38:13PM +0000, Yossi Kuperman wrote:
>
> The bug is there nonetheless, it just doesn't seem to affect anything.
> I guess no one was looking inside the IP header thereafter.
>
> Should I use this instead: 7785bba299a8 ("esp: Add a software GRO codepath")?
Yes, please do this. The Fixes tag tells which stable kernels need
this patch. If we did not have problems before we added GRO, then
there is no need to backport it any further.
Thanks!
prev parent reply other threads:[~2017-06-22 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 8:33 [PATCH net 1/2] xfrm6: Fix IPv6 payload_len in xfrm6_transport_finish yossiku
2017-06-19 8:33 ` [PATCH net 2/2] esp6_offload: Fix IP6CB(skb)->nhoff for ESP GRO yossiku
2017-06-21 5:37 ` [PATCH net 1/2] xfrm6: Fix IPv6 payload_len in xfrm6_transport_finish Steffen Klassert
2017-06-21 11:24 ` Yossi Kuperman
2017-06-21 11:38 ` Steffen Klassert
2017-06-21 15:59 ` Yossi Kuperman
2017-06-21 20:38 ` Yossi Kuperman
2017-06-22 7:15 ` Steffen Klassert [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=20170622071550.GT2631@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=borisp@mellanox.com \
--cc=herbert@gondor.apana.org.au \
--cc=ilant@mellanox.com \
--cc=kliteyn@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=yossiku@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).