linux-kernel - Re: randconfig chosing more than one slab allocator

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: <alpine.DEB.2.00.1203272359290.16201@chino.kir.corp.google.com>
Date:	Wed, 28 Mar 2012 00:04:36 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Pekka Enberg <penberg@...nel.org>
cc:	Sam Ravnborg <sam@...nborg.org>, Michal Marek <mmarek@...e.cz>,
	Arnaud Lacombe <lacombar@...il.com>,
	Christoph Lameter <cl@...ux.com>, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: randconfig chosing more than one slab allocator

On Tue, 27 Mar 2012, Pekka Enberg wrote:

> > > make randconfig seems to allow chosing more than one slab allocator 
> > > although they are all part of a choice,endchoice block (and none are 
> > > tristate).  The following quickly finds both CONFIG_SLUB and CONFIG_SLOB 
> > > enabled:
> > > 
> > > $ while [ 1 ]; do make randconfig &> /dev/null; if [ $(grep "CONFIG_SL[OU]B=y" .config | wc -l) == 2 ]; then break; fi; done
> > > $ grep CONFIG_SL[OU]B=y .config
> > > CONFIG_SLUB=y
> > > CONFIG_SLOB=y
> > 
> > Ping on this?
> 
> I'm fairly sure this is a kbuild issue and that init/Kconfig is correct.
> 

Right, but it happens because SLOB is only available for CONFIG_EXPERT 
(the CONFIG_EMBEDDED restriction dates back to 81819f0fc828 in May 2007) 
so I was wondering if the kconfig folks would know what's going on without 
having to investigate it myself.
--
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/