* Patch "ip6_gre: update mtu properly in ip6gre_err" has been added to the 4.4-stable tree
@ 2017-09-15 17:08 gregkh
2017-09-15 17:18 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: gregkh @ 2017-09-15 17:08 UTC (permalink / raw)
To: lucien.xin, davem, gregkh, jishi; +Cc: stable, stable-commits
This is a note to let you know that I've just added the patch titled
ip6_gre: update mtu properly in ip6gre_err
to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ip6_gre-update-mtu-properly-in-ip6gre_err.patch
and it can be found in the queue-4.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From foo@baz Fri Sep 15 10:03:45 PDT 2017
From: Xin Long <lucien.xin@gmail.com>
Date: Tue, 5 Sep 2017 17:26:33 +0800
Subject: ip6_gre: update mtu properly in ip6gre_err
From: Xin Long <lucien.xin@gmail.com>
[ Upstream commit 5c25f30c93fdc5bf25e62101aeaae7a4f9b421b3 ]
Now when probessing ICMPV6_PKT_TOOBIG, ip6gre_err only subtracts the
offset of gre header from mtu info. The expected mtu of gre device
should also subtract gre header. Otherwise, the next packets still
can't be sent out.
Jianlin found this issue when using the topo:
client(ip6gre)<---->(nic1)route(nic2)<----->(ip6gre)server
and reducing nic2's mtu, then both tcp and sctp's performance with
big size data became 0.
This patch is to fix it by also subtracting grehdr (tun->tun_hlen)
from mtu info when updating gre device's mtu in ip6gre_err(). It
also needs to subtract ETH_HLEN if gre dev'type is ARPHRD_ETHER.
Reported-by: Jianlin Shi <jishi@redhat.com>
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
net/ipv6/ip6_gre.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- a/net/ipv6/ip6_gre.c
+++ b/net/ipv6/ip6_gre.c
@@ -433,7 +433,9 @@ static void ip6gre_err(struct sk_buff *s
}
break;
case ICMPV6_PKT_TOOBIG:
- mtu = be32_to_cpu(info) - offset;
+ mtu = be32_to_cpu(info) - offset - t->tun_hlen;
+ if (t->dev->type == ARPHRD_ETHER)
+ mtu -= ETH_HLEN;
if (mtu < IPV6_MIN_MTU)
mtu = IPV6_MIN_MTU;
t->dev->mtu = mtu;
Patches currently in stable-queue which might be from lucien.xin@gmail.com are
queue-4.4/ip6_gre-update-mtu-properly-in-ip6gre_err.patch
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Patch "ip6_gre: update mtu properly in ip6gre_err" has been added to the 4.4-stable tree
2017-09-15 17:08 Patch "ip6_gre: update mtu properly in ip6gre_err" has been added to the 4.4-stable tree gregkh
@ 2017-09-15 17:18 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2017-09-15 17:18 UTC (permalink / raw)
To: lucien.xin, davem, jishi; +Cc: stable, stable-commits
On Fri, Sep 15, 2017 at 10:08:24AM -0700, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> ip6_gre: update mtu properly in ip6gre_err
>
> to the 4.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> ip6_gre-update-mtu-properly-in-ip6gre_err.patch
> and it can be found in the queue-4.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Nope, sorry, this broke the build, it doesn't look to be needed in 4.4,
sorry for the noise.
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-09-15 17:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-15 17:08 Patch "ip6_gre: update mtu properly in ip6gre_err" has been added to the 4.4-stable tree gregkh
2017-09-15 17:18 ` Greg KH
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).