From: Ashwanth Goli <ashwanth@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, dsahern@gmail.com,
netdev-owner@vger.kernel.org
Subject: Re: [PATCH] ipv6: remove min MTU check for tunnel destinations
Date: Thu, 10 May 2018 19:17:42 +0530 [thread overview]
Message-ID: <0738c72c20d60fd2ffa68573951d0ee3@codeaurora.org> (raw)
In-Reply-To: <20180501.122223.1661453536072731491.davem@davemloft.net>
On 2018-05-01 21:52, David Miller wrote:
> From: Ashwanth Goli <ashwanth@codeaurora.org>
> Date: Mon, 30 Apr 2018 00:36:47 +0530
>
>> With 749439bfac "fix udpv6 sendmsg crash caused by too small MTU"
>> tunnel dst's that report a MTU less than IPV6_MIN_MTU are broken
>> even for packets that are smaller than IPV6_MIN_MTU.
>>
>> According to rfc2473#section-7.1
>>
>> if the original IPv6 packet is equal or smaller than the
>> IPv6 minimum link MTU, the tunnel entry-point node
>> encapsulates the original packet, and subsequently
>> fragments the resulting IPv6 tunnel packet into IPv6
>> fragments that do not exceed the Path MTU to the tunnel
>> exit-point.
>>
>> This patch drops the MTU check for tunnel destinations.
>>
>> Signed-off-by: Ashwanth Goli <ashwanth@codeaurora.org>
>
> RFC 2473 is generally about ipv6 tunnels....
>
>> - if (mtu < IPV6_MIN_MTU)
>> + if (!(rt->dst.flags & DST_XFRM_TUNNEL) && mtu < IPV6_MIN_MTU)
>> return -EINVAL;
>
> But the check you are adding is specifically checking only IPSEC
> tunnels.
>
> If what you say is true in your commit message, this test must
> more generally trigger for all ipv6 tunnel types, not just IPSEC
> ones.
>
> If IPSEC tunnels are being targetting in this patch intentionally,
> that needs to be explained in the commit message.
My intention is to fix the issue for IPSEC tunnels. Will resend by
changing the commit text.
prev parent reply other threads:[~2018-05-10 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 19:06 [PATCH] ipv6: remove min MTU check for tunnel destinations Ashwanth Goli
2018-05-01 16:22 ` David Miller
2018-05-10 13:47 ` Ashwanth Goli [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=0738c72c20d60fd2ffa68573951d0ee3@codeaurora.org \
--to=ashwanth@codeaurora.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).