linux-kernel - Re: [Patch] tipc: use kconfig to limit numeric ranges

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

Message-ID: <4B34413E.7060600@redhat.com>
Date:	Fri, 25 Dec 2009 12:36:14 +0800
From:	Cong Wang <amwang@...hat.com>
To:	Valdis.Kletnieks@...edu
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

Valdis.Kletnieks@...edu wrote:
> 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?
> 

I am not sure, I think the limit of 1 is a temporary choice currently.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/