All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Pravin Shelar <pshelar@ovn.org>,
	netdev@vger.kernel.org
Subject: [PATCH net 0/3] vti4, ip_tunnel: Fixes for MTU assignment and validation
Date: Thu, 15 Mar 2018 17:16:26 +0100	[thread overview]
Message-ID: <cover.1521068627.git.sbrivio@redhat.com> (raw)

Patch 1/3 re-introduces a fix to ensure that default MTU on new
link is not lowered unnecessarily because of double counting of
headers. This fix was originally introduced in 2014 and got lost
in a merge commit shortly afterwards.

Patches 2/3 and 3/3 ensure that MTU passed from userspace on link
creation is taken into account and also properly validated.

Stefano Brivio (3):
  vti4: Don't count header length twice on tunnel setup
  ip_tunnel: Clamp MTU to bounds on new link
  vti4: Don't override MTU passed on link creation via IFLA_MTU

 net/ipv4/ip_tunnel.c | 8 +++++++-
 net/ipv4/ip_vti.c    | 2 --
 2 files changed, 7 insertions(+), 3 deletions(-)

-- 
2.15.1

             reply	other threads:[~2018-03-15 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 16:16 Stefano Brivio [this message]
2018-03-15 16:16 ` [PATCH net 1/3] vti4: Don't count header length twice on tunnel setup Stefano Brivio
2018-03-15 16:16 ` [PATCH net 2/3] ip_tunnel: Clamp MTU to bounds on new link Stefano Brivio
2018-03-15 16:16 ` [PATCH net 3/3] vti4: Don't override MTU passed on link creation via IFLA_MTU Stefano Brivio
2018-03-17 23:46 ` [PATCH net 0/3] vti4, ip_tunnel: Fixes for MTU assignment and validation David Miller
2018-03-19 10:20   ` 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.1521068627.git.sbrivio@redhat.com \
    --to=sbrivio@redhat.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.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 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.