netdev - Re: [PATCH net-next] Re: rib_trie / Fix inflate_threshold

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: <20090720.074123.75633320.davem@davemloft.net>
Date:	Mon, 20 Jul 2009 07:41:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jarkao2@...il.com
Cc:	pstaszewski@...are.pl, netdev@...r.kernel.org, robert@...ur.slu.se,
	jorge@...2.net
Subject: Re: [PATCH net-next] Re: rib_trie / Fix inflate_threshold_root.
 Now=15 size=11 bits

From: Jarek Poplawski <jarkao2@...il.com>
Date: Tue, 14 Jul 2009 21:41:00 +0200

> ipv4: Fix inflate_threshold_root automatically
> 
> During large updates there could be triggered warnings like: "Fix
> inflate_threshold_root. Now=25 size=11 bits" if inflate() of the root
> node isn't finished in 10 loops. It should be much rarer now, after
> changing the threshold from 15 to 25, and a temporary problem, so
> this patch tries to handle it automatically using a fix variable to
> increase by one inflate threshold for next root resizes (up to the 35
> limit, max fix = 10). The fix variable is decreased when root's
> inflate() finishes below 7 loops (even if some other, smaller table/
> trie is updated -- for simplicity the fix variable is global for now).
> 
> Reported-by: Pawel Staszewski <pstaszewski@...are.pl>
> Reported-by: Jorge Boncompte [DTI2] <jorge@...2.net>
> Tested-by: Pawel Staszewski <pstaszewski@...are.pl>
> Signed-off-by: Jarek Poplawski <jarkao2@...il.com>

Applied.
--
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