From: Sabrina Dubroca <sd@queasysnail.net>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@gmail.com>,
Stefano Brivio <sbrivio@redhat.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: [PATCH net v2 0/2] net: ipv4: fixes for PMTU when link MTU changes
Date: Tue, 9 Oct 2018 17:48:13 +0200 [thread overview]
Message-ID: <cover.1539073548.git.sd@queasysnail.net> (raw)
The first patch adapts the changes that commit e9fa1495d738 ("ipv6:
Reflect MTU changes on PMTU of exceptions for MTU-less routes") did in
IPv6 to IPv4: lower PMTU when the first hop's MTU drops below it, and
raise PMTU when the first hop was limiting PMTU discovery and its MTU
is increased.
The second patch fixes bugs introduced in commit d52e5a7e7ca4 ("ipv4:
lock mtu in fnhe when received PMTU < net.ipv4.route.min_pmtu") that
only appear once the first patch is applied.
Selftests for these cases were introduced in net-next commit
e44e428f59e4 ("selftests: pmtu: add basic IPv4 and IPv6 PMTU tests")
v2: add cover letter, and fix a few small things in patch 1
Sabrina Dubroca (2):
net: ipv4: update fnhe_pmtu when first hop's MTU changes
net: ipv4: don't let PMTU updates increase route MTU
include/linux/netdevice.h | 7 ++++++
include/net/ip_fib.h | 1 +
net/core/dev.c | 28 ++++++++++++++++++++--
net/ipv4/fib_frontend.c | 12 ++++++----
net/ipv4/fib_semantics.c | 50 +++++++++++++++++++++++++++++++++++++++
net/ipv4/route.c | 7 +++---
6 files changed, 96 insertions(+), 9 deletions(-)
--
2.19.0
next reply other threads:[~2018-10-09 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 15:48 Sabrina Dubroca [this message]
2018-10-09 15:48 ` [PATCH net v2 1/2] net: ipv4: update fnhe_pmtu when first hop's MTU changes Sabrina Dubroca
2018-10-10 15:27 ` David Ahern
2018-10-09 15:48 ` [PATCH net v2 2/2] net: ipv4: don't let PMTU updates increase route MTU Sabrina Dubroca
2018-10-11 5:45 ` [PATCH net v2 0/2] net: ipv4: fixes for PMTU when link MTU changes David Miller
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=cover.1539073548.git.sd@queasysnail.net \
--to=sd@queasysnail.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@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 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.