Messages in this thread | | | Date | Wed, 28 Mar 2012 00:04:36 -0700 (PDT) | From | David Rientjes <> | 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.
| |