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: <31665.1261713006@localhost>
Date:	Thu, 24 Dec 2009 22:50:06 -0500
From:	Valdis.Kletnieks@...edu
To:	Amerigo Wang <amwang@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Allan Stephens <allan.stephens@...driver.com>,
	netdev@...r.kernel.org, Per Liden <per.liden@...csson.com>,
	tipc-discussion@...ts.sourceforge.net, akpm@...ux-foundation.org,
	Jon Maloy <jon.maloy@...csson.com>
Subject: Re: [Patch] tipc: use kconfig to limit numeric ranges

On Thu, 24 Dec 2009 22:26:48 EST, Amerigo Wang said:
> We can rely on kconfig to limit these numbers,
> no need to limit them at compile time/run time.

> +          ***Only 1 (one cluster in a zone) is supported by current code.***
>  
>            (Max number of clusters inside TIPC zone. Max supported 
>            value is 4095 clusters, minimum is 1.

Given the limit of 1, maybe the reference to 4095 should be nuked?


Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ