linux-kernel - Re: [GFS2] Fix Kconfig [2/2]

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]

Date:	Mon, 18 Dec 2006 11:10:40 +0000
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	cluster-devel@...hat.com, linux-kernel@...r.kernel.org,
	Patrick Caulfield <pcaulfie@...hat.com>,
	Chris Zubrzycki <chris@...dle--earth.org>,
	Adrian Bunk <bunk@...sta.de>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Toralf Förster <toralf.foerster@....de>,
	Aleksandr Koltsoff <czr@....fi>
Subject: Re: [GFS2] Fix Kconfig [2/2]

Hi,

On Mon, 2006-12-18 at 11:50 +0100, Jan Engelhardt wrote:
> On Dec 18 2006 09:57, Steven Whitehouse wrote:
> > config GFS2_FS_LOCKING_DLM
> > 	tristate "GFS2 DLM locking module"
> >-	depends on GFS2_FS
> >+	depends on GFS2_FS && NET && INET && (IPV6 || IPV6=n)
> 
> What is this supposed to do? IPV6 || IPV6=n is a tautology AFAICS.
> 
> 
> 	-`J'

It looks odd, I'll grant you, but see the thread entitled "Re: [PATCH]
Remove logically superfluous comparisons from Kconfig files." and the
answer that Russell King has just given on the same subject where he
says:

>config FOO
>        tristate 'foo'
>        depends on BAR || BAR=n
>
>is not superfluous.  The allowed states for FOO with the above
>construct are (assuming modules are enabled):
>
>        BAR     FOO
>        Y       Y,M,N
>        M       M,N
>        N       Y,M,N

which hopefully explains it a bit better,

Steve.


-
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/