From: Stefano Brivio <sbrivio@redhat.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: Sabrina Dubroca <sd@queasysnail.net>,
Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Alexey Kodanev <alexey.kodanev@oracle.com>,
Jarod Wilson <jarod@redhat.com>,
netdev@vger.kernel.org
Subject: [PATCH net 0/3] vti6: Fixes for MTU assignment and validation
Date: Thu, 15 Mar 2018 17:17:10 +0100 [thread overview]
Message-ID: <cover.1521128962.git.sbrivio@redhat.com> (raw)
This series introduces fixes to ensure that default MTU
assignment for vti6 is properly calculated (and to make it
consistent with vti4), to ensure we always use the MTU from
userspace (and validate it), if given, when a link is created or
changed, and that the MTU upper bound is properly set.
Stefano Brivio (3):
vti6: Properly adjust vti6 MTU from MTU of lower device
vti6: Keep set MTU on link creation or change, validate it
vti6: Fix dev->max_mtu setting
net/ipv6/ip6_vti.c | 36 +++++++++++++++++++++++-------------
1 file changed, 23 insertions(+), 13 deletions(-)
--
2.15.1
next reply other threads:[~2018-03-15 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 16:17 Stefano Brivio [this message]
2018-03-15 16:17 ` [PATCH net 1/3] vti6: Properly adjust vti6 MTU from MTU of lower device Stefano Brivio
2018-03-15 16:17 ` [PATCH net 2/3] vti6: Keep set MTU on link creation or change, validate it Stefano Brivio
2018-03-15 16:17 ` [PATCH net 3/3] vti6: Fix dev->max_mtu setting Stefano Brivio
2018-03-19 10:20 ` [PATCH net 0/3] vti6: Fixes for MTU assignment and validation 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=cover.1521128962.git.sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=alexey.kodanev@oracle.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jarod@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.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).