From: David Miller <davem@davemloft.net>
To: sd@queasysnail.net
Cc: netdev@vger.kernel.org, dsahern@gmail.com, sbrivio@redhat.com
Subject: Re: [PATCH net v2 0/2] net: ipv4: fixes for PMTU when link MTU changes
Date: Wed, 10 Oct 2018 22:45:28 -0700 (PDT) [thread overview]
Message-ID: <20181010.224528.939874574357827165.davem@davemloft.net> (raw)
In-Reply-To: <cover.1539073548.git.sd@queasysnail.net>
From: Sabrina Dubroca <sd@queasysnail.net>
Date: Tue, 9 Oct 2018 17:48:13 +0200
> 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
Series applied and queued up for -stable.
prev parent reply other threads:[~2018-10-11 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 15:48 [PATCH net v2 0/2] net: ipv4: fixes for PMTU when link MTU changes Sabrina Dubroca
2018-10-09 15:48 ` [PATCH net v2 1/2] net: ipv4: update fnhe_pmtu when first hop's " 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 ` David Miller [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=20181010.224528.939874574357827165.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
/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).