netdev - [PATCH 0/2 v2] Fix ipv6 routing table entry limit.

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>] [day] [month] [year] [list]

Message-Id: <20110624.164706.1200327249570461124.davem@davemloft.net>
Date:	Fri, 24 Jun 2011 16:47:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
CC:	sim@...tway.ca
Subject: [PATCH 0/2 v2] Fix ipv6 routing table entry limit.

As discussed in other threads, the routing table lives in the same
data structure as cached routing entries.  This enforces a false
limit on the number of routing table entries one can install
on ipv6 and this is becomming a real problem for people.

Fix this by adding a DST_NOCOUNT flag and use it for ipv6 routing
table entries.

No special handling is necessary when cloning or copying since
the flags are never directly copied by the clone/copy code in
ipv6.

This is a 2 patch series now in order to sanitize the dst->flags
setting done in net/ipv6/route.c

I've tested this by adding and removing ~16K ipv6 routes over
and over again, the routing cache limit never got hit.

Simon, you'll need to work out that crash you were seeing since
I can't reproduce it on any of my machines.
--
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