netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Julian Anastasov <ja@ssi.bg>,
	timo.teras@iki.fi, luky-37@hotmail.com, pupilla@libero.it,
	netdev@vger.kernel.org
Subject: [PATCH 2/2] ipv4: Don't update the pmtu on mtu locked routes
Date: Thu, 17 Jan 2013 07:58:10 +0100	[thread overview]
Message-ID: <20130117065810.GH18940@secunet.com> (raw)
In-Reply-To: <20130117065500.GG18940@secunet.com>

Routes with locked mtu should not use learned pmtu informations,
so do not update the pmtu on these routes.

Reported-by: Julian Anastasov <ja@ssi.bg>
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
 net/ipv4/route.c |    3 +++
 1 file changed, 3 insertions(+)

diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 6e4a89c..259cbee 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -912,6 +912,9 @@ static void __ip_rt_update_pmtu(struct rtable *rt, struct flowi4 *fl4, u32 mtu)
 	struct dst_entry *dst = &rt->dst;
 	struct fib_result res;
 
+	if (dst_metric_locked(dst, RTAX_MTU))
+		return;
+
 	if (dst->dev->mtu < mtu)
 		return;
 
-- 
1.7.9.5

  reply	other threads:[~2013-01-17  6:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  6:55 [PATCH 1/2] ipv4: Remove output route check in ipv4_mtu Steffen Klassert
2013-01-17  6:58 ` Steffen Klassert [this message]
2013-01-17  8:40   ` [PATCH 2/2] ipv4: Don't update the pmtu on mtu locked routes David Miller
2013-01-17  8:41   ` Julian Anastasov
2013-01-17  8:35 ` [PATCH 1/2] ipv4: Remove output route check in ipv4_mtu Timo Teras
2013-01-17  8:40 ` 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=20130117065810.GH18940@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=ja@ssi.bg \
    --cc=luky-37@hotmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pupilla@libero.it \
    --cc=timo.teras@iki.fi \
    /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).