linux-kernel - Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

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: <CA+55aFxpH2A5pTkeAt-bapN6Erac7SSEUhS9qaZ6jUhm_0EAtA@mail.gmail.com>
Date:	Mon, 11 Feb 2013 15:32:26 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	David Rientjes <rientjes@...gle.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Pekka Enberg <penberg@...nel.org>,
	Michal Marek <mmarek@...e.cz>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

On Mon, Feb 11, 2013 at 9:58 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> So basically Pekka optimistically thought it's an eventual 'tit
> for tat', a constant stream of benefits to the kernel, in the
> hope of finding a home in the upstream kernel which would
> further help both projects. The kernel wants to keep the 'tit'
> only though.

Ingo, stop this idiotic nonsense.

You seem to think that "kvmtool is useful for kernel" is somehow relevant.

IT IS TOTALLY IRRELEVANT.

"sparse" is useful for kernel development. "git" is useful for kernel
development. "xterm" is useful for kernel development.

See a pattern? We have tons of tools that are helping develop the
kernel, and for absolutely NONE of them is that at all an argument for
merging them into the kernel.

If the Xen people came and asked me to merge their virtualizer code
into the kernel, I'd call them idiots.

Why is kvmtool so magical that you use this argument for merging it
into the kernel?

It makes no sense.

Yet you continue to use it as if it was somehow an argument for
merging it. Despite the hundreds of projects to the contrary.

So this whole "constant stream of benefits" you talk about is PURE AND
UTTER GARBAGE. And that's not a commentary on whether it is true or
not, it's a commentary on the fact that it is entirely irrelevant to
whether something should be merged.

Merging two projects does not make them easier to maintain. Quite the
reverse. It just ties the maintenance together in irrelevant ways.

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