From: Steffen Klassert <steffen.klassert@secunet.com>
To: Mark McKinstry <Mark.McKinstry@alliedtelesis.co.nz>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"alexander.h.duyck@redhat.com" <alexander.h.duyck@redhat.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH] vti6: Add pmtu handling to vti6_xmit.
Date: Fri, 4 Mar 2016 08:05:25 +0100 [thread overview]
Message-ID: <20160304070525.GA3347@gauss.secunet.com> (raw)
In-Reply-To: <56CE22A3.7030702@alliedtelesis.co.nz>
On Wed, Feb 24, 2016 at 09:37:39PM +0000, Mark McKinstry wrote:
> On 19/02/16 01:19, Steffen Klassert wrote:
> > On Thu, Feb 18, 2016 at 01:40:00AM +0000, Mark McKinstry wrote:
> >> This patch fixes our issue, thanks. In our scenario the tunnel path MTU
> >> now gets updated so that subsequent large packets sent over the tunnel
> >> get fragmented correctly.
> > I've applied this patch to the ipsec tree now.
> > Thanks for testing!
> I spoke too soon. Upon further testing with this patch we have found it
> causes
> a skt buffer leak. This is problematic for us and can cause memory
> exhaustion in
> one of our test scenarios that has an IPv4 IPsec tunnel over a PPP link.
The patch below is what I plan to apply on top of the original patch.
Subject: [PATCH] vti: Fix recource leeks on pmtu discovery
A recent patch introduced pmtu handling directly in the
vti transmit routine. Unfortunately we now return without
releasing the dst_entry and freeing the sk_buff. This patch
fixes the issue.
Fixes: 325b71fe0f57 ("vti: Add pmtu handling to vti_xmit.")
Reported-by: Mark McKinstry <Mark.McKinstry@alliedtelesis.co.nz>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
net/ipv4/ip_vti.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/ip_vti.c b/net/ipv4/ip_vti.c
index 6862305..2ea2b6e 100644
--- a/net/ipv4/ip_vti.c
+++ b/net/ipv4/ip_vti.c
@@ -206,7 +206,8 @@ static netdev_tx_t vti_xmit(struct sk_buff *skb, struct net_device *dev,
else
icmpv6_send(skb, ICMPV6_PKT_TOOBIG, 0, mtu);
- return -EMSGSIZE;
+ dst_release(dst);
+ goto tx_error;
}
err = dst_output(tunnel->net, skb->sk, skb);
--
1.9.1
next prev parent reply other threads:[~2016-03-04 7:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 17:40 [PATCH] xfrm6: Do not use xfrm_local_error for path MTU issues in tunnels Alexander Duyck
2015-05-28 4:49 ` Herbert Xu
2015-05-28 4:56 ` Steffen Klassert
2015-05-28 5:36 ` Steffen Klassert
2015-05-28 7:18 ` Alexander Duyck
2015-05-28 8:40 ` Steffen Klassert
2015-05-28 19:15 ` Alexander Duyck
2015-05-29 16:53 ` Alexander Duyck
2015-05-29 18:28 ` [PATCH] vti6: Add pmtu handling to vti6_xmit Alexander Duyck
2015-06-01 23:04 ` David Miller
2016-02-10 1:50 ` Mark McKinstry
2016-02-17 7:08 ` Steffen Klassert
2016-02-18 1:40 ` Mark McKinstry
2016-02-18 12:19 ` Steffen Klassert
2016-02-24 21:37 ` Mark McKinstry
2016-02-25 11:21 ` Steffen Klassert
2016-03-04 7:05 ` Steffen Klassert [this message]
2016-03-14 21:52 ` Mark McKinstry
2016-03-15 12:28 ` Steffen Klassert
2016-03-22 10:53 ` Steffen Klassert
2016-03-30 21:04 ` Mark McKinstry
2016-04-01 8:08 ` Steffen Klassert
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=20160304070525.GA3347@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=Mark.McKinstry@alliedtelesis.co.nz \
--cc=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.