netdev - Re: Rate Limitation of Router Reachability Probing for possible dead routers (is Re: ipv6: Do not depend on rt->n in rt6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 22 Jan 2013 00:49:39 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	yoshfuji@...ux-ipv6.org
Cc:	netdev@...r.kernel.org
Subject: Re: Rate Limitation of Router Reachability Probing for possible
 dead routers (is Re: ipv6: Do not depend on rt->n in rt6_probe().)

From: YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
Date: Tue, 22 Jan 2013 12:47:42 +0900

> It seems that we removed check for gc_thresh1 (number of
> minimum entries) in neigh_alloc() during 2.3.x but I cannot
> remember the reason (or just I do not know it).

You seem to suggest that neigh_periodic_work() should check gc_thresh1
and I agree with this idea.

Considering how neighbour references work now, what it does currently
doesn't make any sense.

Right now it runs over and over again, unconditionally, and purges
entries even if there are very few of them.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html