From: David Ahern <dsahern@gmail.com>
To: Kaustubh Pandey <kapandey@codeaurora.org>,
Stefano Brivio <sbrivio@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sharathv@codeaurora.org, chinagar@codeaurora.org
Subject: Re: [PATCH] ipv6: Honor route mtu if it is within limit of dev mtu
Date: Wed, 24 Feb 2021 13:28:49 -0700 [thread overview]
Message-ID: <ef380be3-0a87-9599-f3ea-ec7779ad5db1@gmail.com> (raw)
In-Reply-To: <1614011555-21951-1-git-send-email-kapandey@codeaurora.org>
On 2/22/21 9:32 AM, Kaustubh Pandey wrote:
> When netdevice MTU is increased via sysfs, NETDEV_CHANGEMTU is raised.
>
> addrconf_notify -> rt6_mtu_change -> rt6_mtu_change_route ->
> fib6_nh_mtu_change
>
> As part of handling NETDEV_CHANGEMTU notification we land up on a
> condition where if route mtu is less than dev mtu and route mtu equals
> ipv6_devconf mtu, route mtu gets updated.
>
> Due to this v6 traffic end up using wrong MTU then configured earlier.
> This commit fixes this by removing comparison with ipv6_devconf
> and updating route mtu only when it is greater than incoming dev mtu.
>
> This can be easily reproduced with below script:
> pre-condition:
> device up(mtu = 1500) and route mtu for both v4 and v6 is 1500
>
> test-script:
> ip route change 192.168.0.0/24 dev eth0 src 192.168.0.1 mtu 1400
> ip -6 route change 2001::/64 dev eth0 metric 256 mtu 1400
> echo 1400 > /sys/class/net/eth0/mtu
> ip route change 192.168.0.0/24 dev eth0 src 192.168.0.1 mtu 1500
> echo 1500 > /sys/class/net/eth0/mtu
>
> Signed-off-by: Kaustubh Pandey <kapandey@codeaurora.org>
> ---
> net/ipv6/route.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index 1536f49..653b6c7 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -4813,8 +4813,7 @@ static int fib6_nh_mtu_change(struct fib6_nh *nh, void *_arg)
> struct inet6_dev *idev = __in6_dev_get(arg->dev);
> u32 mtu = f6i->fib6_pmtu;
>
> - if (mtu >= arg->mtu ||
> - (mtu < arg->mtu && mtu == idev->cnf.mtu6))
> + if (mtu >= arg->mtu)
> fib6_metric_set(f6i, RTAX_MTU, arg->mtu);
>
> spin_lock_bh(&rt6_exception_lock);
>
The existing logic mirrors what is done for exceptions, see
rt6_mtu_change_route_allowed and commit e9fa1495d738.
It seems right to me to drop the mtu == idev->cnf.mtu6 comparison in
which case the exceptions should do the same.
Added author of e9fa1495d738 in case I am overlooking something.
Test case should be added to tools/testing/selftests/net/pmtu.sh, and
did you run that script with the proposed change?
prev parent reply other threads:[~2021-02-24 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:32 Kaustubh Pandey
2021-02-24 18:47 ` Jakub Kicinski
2021-02-24 20:28 ` David Ahern [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=ef380be3-0a87-9599-f3ea-ec7779ad5db1@gmail.com \
--to=dsahern@gmail.com \
--cc=chinagar@codeaurora.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kapandey@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sharathv@codeaurora.org \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®