linux-kernel - Re: linux-cr ported to 3.2-rc1

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:	Thu, 5 Jan 2012 22:07:52 +0100
From:	Adrian Reber <adrian@...as.de>
To:	Pavel Emelyanov <xemul@...allels.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Serge E. Hallyn" <serge@...lyn.com>,
	Oren Laadan <orenl@...columbia.edu>,
	"matt.helsley@...il.com" <matt.helsley@...il.com>,
	Peter Väterlein 
	<Peter.Vaeterlein@...esslingen.de>
Subject: Re: linux-cr ported to 3.2-rc1

On Mon, Nov 14, 2011 at 07:20:03PM +0400, Pavel Emelyanov wrote:
> On 11/14/2011 07:13 PM, Adrian Reber wrote:
> > I have ported the linux-cr patches from www.linux-cr.org/pub/git/linux-cr.git
> > to the latest kernel (3.2-rc1). The tests (on x86_64) I have done so far
> > were successful. My repository with the C/R patches on top of 3.2-rc1 is
> > currently at:
> > 
> > http://lisas.de/~adrian/linux-cr.git
> > 
> > 
> > The development on the linux-cr tree hast stopped sometime around 2.6.37
> > and although those patches have gone through many revisions I am not sure
> > about the latest state of those patches concerning inclusion. At what
> > point has the discussion stopped and why?
> 
> AFAIK very few people from the community support the idea of having the C/R
> functionality implemented as the kernel subsystem.

Ah. Okay. I still ported those patches to 3.2 so that there exists a
working C/R until you have released your code.

http://lisas.de/~adrian/cr/3.2/linux-cr.git

> > I have seen patches from Pavel about another approach for 
> > checkpointing/restarting but I haven't heard anything about
> > that during the last months.
> > 
> > What are the chances to get one of the checkpointing/restarting
> > implementations included. What is still missing from the one I used?
> 
> The chances are ... quite high. We implement our C/R code in the userspace
> and require very few pieces from kernel. So far 2 out of 3 proposed API
> extensions were merged into -mm tree.
> 
> > What is the latest state of Pavel's patches?
> 
> The state right now is - we can dump and restore tasks with any types of
> memory, open regular files and pipes with its contents. The code is currently 
> under internal review process. We're going to send the public RFC early next 
> week. Then go on with more resources to dump and restore.

I am interested in C/R and if your code has better chances going
upstream then I would be interested seeing those patches and working
with you. As long as I do not have your code I will keep on working with
the patches I currently have and which seem to be running pretty good on
3.2 so far.

The first set of patches in my current patchset tries to implement
eclone() which provides the clone() functionality but with the
possibility to request a certain PID so that child processes can be
restarted with the same PID. How are you planning to restart child
processes? Are those patches maybe something which makes also sense for
your C/R implementation?

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