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]

Date:	Sat, 9 Feb 2013 21:39:27 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	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>, Michal Marek <mmarek@...e.cz>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

On Sat, Feb 9, 2013 at 8:07 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> Everything you said was about how it's more convenient for you and
> Ingo, not at all about why it should be better for anybody else. You
> haven't bothered to even try making it an external project, so it
> doesn't compile that way. You're the only one working on it, so being
> convenient for you is the primary issue. Arguments like that actively
> make me not want to merge it, because they are only arguments for you
> continuing to work the way you have, not arguments for why the project
> would make sense to merge into the main kernel repository.

You are so full of shit it's not even funny.

I am *not* the only person working on the project, far from it. I'm not
trying to make things easy for me, I'm trying to build on the strenghts
of tools/kvm.

The main argument for merging into the main kernel repository has always been
that (we think) it improves the kernel because significant amount of
development is directly linked to kernel code (think KVM ARM port here, for
example). The secondary argument has been to make it easy for kernel developers
to work on both userspace and kernel in tandem (like has happened with vhost
drivers). In short: it speeds up development of Linux virtualization code.

It's not as if there's anything new here so I didn't think it was
necessary to rehash the old arguments. I know you don't have a
compelling reason to pull and that's fine. Just don't come up with these
lame excuses that have nothing to do with reality.

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