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: <20130206214646.GA28135@gmail.com>
Date:	Wed, 6 Feb 2013 22:46:46 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	David Rientjes <rientjes@...gle.com>,
	Pekka Enberg <penberg@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	Randy Dunlap <rdunlap@...radead.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Michal Marek <mmarek@...e.cz>,
	"H. Peter Anvin" <hpa@...or.com>, tglx@...utronix.de,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)


* Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi David,
> 
> On Wed, 6 Feb 2013 12:12:57 -0800 (PST) David Rientjes <rientjes@...gle.com> wrote:
> >
> > On Wed, 6 Feb 2013, Pekka Enberg wrote:
> > 
> > > > Yeah, that's a good idea - I think Pekka can apply that change
> > > > just fine to help anyone doing merges - I don't think kconfig
> > > > treats it as a fatal error.
> > > 
> > > Applied, thanks guys!
> > 
> > Adding Stephen to the cc.
> > 
> > What's the endgame for kvmtool/next?  The patch that this fixes has been 
> > sitting in linux-next for over 15 months and hasn't been pulled by Linus, 
> > yet some find it to be quite useful.
> > 
> > Is it a permanent addition to linux-next, is there a route to mainline, 
> > or something else?
> 
> Linus has said that he will not take the kvmtool tree in its 
> current form, but would prefer that it be a separate project, 
> so I should really drop it from linux-next (and ask the tip 
> guys to remove it from their auto-latest branch).
> 
> I have actually been meaning to get back to this, so, today I 
> will drop the kvmtool tree and, Ingo, if you could (at your 
> convenience i.e. when you are next rebasing it) remove it from 
> tip/auto-latest, thanks.

Pekka still intends to send it in the next merge window AFAIK, 
and I use it for testing rather frequently so I'm not going to 
remove it from my tree for the time being.

Note that I never actually had any maintenance problems due to 
it: it's orthogonal, and as long as you don't use it explicitly 
(such as its 'make kvmconfig' feature - which is rather handy) 
it never actually broke anything.

Thanks,

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