linux-kernel - Re: [PATCH 18/38] C/R: core stuff

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: <20090528153852.GC18256@x200.localdomain>
Date:	Thu, 28 May 2009 19:38:52 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	"Serge E. Hallyn" <serge@...lyn.com>
Cc:	akpm@...ux-foundation.org, xemul@...allels.com,
	containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 18/38] C/R: core stuff

On Tue, May 26, 2009 at 06:44:36PM -0500, Serge E. Hallyn wrote:
> Quoting Alexey Dobriyan (adobriyan@...il.com):
> > And since you guys showed that just idea of in-kernel checkpointing is not
> > rejected outright, it doesn't mean that you can drag every single idea too.
> 
> Can you rephrase here?  I have no idea what you mean by 'drag every single
> idea'

  									complexity
 +-|------------------------------------------------|----------------------|-->
hypervisor C/R					in-kernel C/R	C/R for unpriviledged
								C/R with "leaks"

I personally thought in-kernel C/R will be rejected outright, but it wasn't.
This in theory doesn't mean other two issues should be accepted.
--
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/