linux-kernel - Re: [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for building working KVM guest kernels

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:	Fri, 03 May 2013 07:54:36 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Borislav Petkov <bp@...en8.de>
CC:	Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	David Rientjes <rientjes@...gle.com>, hpa@...or.com,
	linux-kernel@...r.kernel.org, penberg@...nel.org,
	levinsasha928@...il.com, mtosatti@...hat.com, tglx@...utronix.de,
	bp@...e.de, fengguang.wu@...el.com,
	linux-tip-commits@...r.kernel.org, Michal Marek <mmarek@...e.cz>
Subject: Re: [tip:x86/urgent] x86/kconfig:  Add a Kconfig shortcut for building
 working KVM guest kernels

On 05/03/13 07:29, Borislav Petkov wrote:
> On Thu, May 02, 2013 at 10:07:03PM +0200, Borislav Petkov wrote:a
>> I wonder if one can exclude options from randconfig until 'select' has
>> been taught to resolve dependencies...
> 
> So I talked to Michal on IRC about the whole deal and the fact of the
> matter is, unless someone steps up and rewrites the Kconfig solver so
> that selects work as expected, this option would break whenever one
> of those selected option's dependencies change or said option is made
> configurable.
> 
> Which means, the next best thing would be to have a small file
> somewhere, maybe in scripts/kconfig/ or so, called 'allrand.config' and
> which has default settings for randconfig builds. It would have
> 
> # CONFIG_KVM_GUEST_COMMON_OPTIONS is not set
> 
> so that this option is always disabled in randconfigs.
> 
> Frankly, I much rather prefer this than going nuts and including every
> possible dependency just so some obscure randconfigs don't break (that's
> not the point of this option anyway); and then having to run around and
> fix it once some of the selected option's dependencies change.
> 
> Opinions?


Could you alternately have a kvm_guest.config that should always work
for you?


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