netdev - Re: [RFC PATCH] dont create cached routes from ARP requests

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4C9CBCFC.6080300@gmail.com>
Date:	Fri, 24 Sep 2010 17:00:12 +0200
From:	Ulrich Weber <ulrich.weber@...glemail.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
CC:	Ulrich Weber <uweber@...aro.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [RFC PATCH] dont create cached routes from ARP requests

Hi Eric,

please find the output in the attached text file.

Neighbor garbage collection wont't work because all
neighbor records are bound to cached routes.

Forced route garbaged collections returns without freeing
any routes, probably because the route threshold is quite high
with 65536 compared to the small neighbor threshold of 1024,
resulting in a fixed amount of 1024 cached routes...

Instead of running the garbage collection we could flush the route
cache completely if the neighbor cache overflows.
But why do we have to cache that routes in first place ?
See the previous patch which skips caching for that kind of routes.

Cheers
 Ulrich

View attachment "cache_debug.txt" of type "text/plain" (8009 bytes)