From: Ben Greear <greearb@candelatech.com>
To: netdev@vger.kernel.org
Cc: Ben Greear <greearb@candelatech.com>
Subject: [PATCH 2/2] IPv6: Warn users when route/max_entries is reached.
Date: Mon, 8 Nov 2010 11:13:49 -0800 [thread overview]
Message-ID: <1289243629-20789-2-git-send-email-greearb@candelatech.com> (raw)
In-Reply-To: <1289243629-20789-1-git-send-email-greearb@candelatech.com>
Signed-off-by: Ben Greear <greearb@candelatech.com>
---
:100644 100644 a275c6e... 348b34c... M net/ipv6/route.c
net/ipv6/route.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/net/ipv6/route.c b/net/ipv6/route.c
index a275c6e..348b34c 100644
--- a/net/ipv6/route.c
+++ b/net/ipv6/route.c
@@ -1060,8 +1060,12 @@ static int ip6_dst_gc(struct dst_ops *ops)
unsigned long rt_last_gc = net->ipv6.ip6_rt_last_gc;
if (time_after(rt_last_gc + rt_min_interval, now) &&
- atomic_read(&ops->entries) <= rt_max_size)
+ atomic_read(&ops->entries) <= rt_max_size) {
+ if (net_ratelimit())
+ pr_warning("IPv6: Maximum number of routes reached,"
+ " consider increasing route/max_size.\n");
goto out;
+ }
net->ipv6.ip6_rt_gc_expire++;
fib6_run_gc(net->ipv6.ip6_rt_gc_expire, net);
--
1.6.2.5
next prev parent reply other threads:[~2010-11-08 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 19:13 [PATCH 1/2] docs: Add neigh/gc_thresh3 and route/max_size documentation Ben Greear
2010-11-08 19:13 ` Ben Greear [this message]
2010-11-08 21:09 ` [PATCH 2/2] IPv6: Warn users when route/max_entries is reached Ben Greear
2010-11-08 21:22 ` David Miller
2010-11-12 22:04 ` [PATCH 1/2] docs: Add neigh/gc_thresh3 and route/max_size documentation 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=1289243629-20789-2-git-send-email-greearb@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/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.