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]

Message-ID: <20130501222850.GB15623@pd.tnic>
Date:	Thu, 2 May 2013 00:28:50 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org, Pekka Enberg <penberg@...nel.org>,
	levinsasha928@...il.com, mtosatti@...hat.com, tglx@...utronix.de,
	Borislav Petkov <bp@...e.de>, fengguang.wu@...el.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86/kconfig:  Add a Kconfig shortcut for
 building working KVM guest kernels

On Wed, May 01, 2013 at 03:09:13PM -0700, David Rientjes wrote:
> Unfortunately, the way you're implementing KVM_GUEST_COMMON_OPTIONS
> will typically result in this if the options you "select" get new
> dependencies in the future. So you'll always be updating this option
> constantly with these types of problems.

Ok, so let's step back a bit here: I've added this option with the idea
to have it as a shortcut so that you don't go search for every commodity
option when you want to boot the kernel as a kvm guest. Currently I have
it in all.config when doing randconfig builds here. While I'm doing the
randbuilds, why not boot it in kvm too while at it.

Now, I really fail to see what you describe above to be a fairly normal
use case. I'm sure you can take Kconfig and abuse it so that it screams
all kinds of errors and we know select is evil and Kconfig is not
perfect, etc, etc...

So I'm pretty sure we won't be able to plug all holes. However, let's
try to plug only those which hinder *real* usage instead of contrived
stuff.

So, let's start again: is this something real you're triggering
with some random testing you're doing or are you simply
abusing^Wexperimenting with Kconfig and staring at what breaks?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/