linux-kernel - Re: [C/R v20][PATCH 00/96] Linux Checkpoint-Restart

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] [day] [month] [year] [list]

Message-Id: <20100401165754.9fe93085.akpm@linux-foundation.org>
Date:	Thu, 1 Apr 2010 16:57:54 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>,
	containers@...ts.linux-foundation.org,
	Oren Laadan <orenl@...columbia.edu>
Subject: Re: [C/R v20][PATCH 00/96] Linux Checkpoint-Restart - v20

On Thu, 1 Apr 2010 18:37:10 -0500
"Serge E. Hallyn" <serue@...ibm.com> wrote:

> Quoting Oren Laadan (orenl@...columbia.edu):
> > Hi Andrew,
> > 
> > Following up on the thread on the checkpoint-restart patch set
> > (http://lkml.org/lkml/2010/3/1/422), the following series is the
> > latest checkpoint/restart, based on 2.6.33.
> > 
> > The first 20 patches are cleanups and prepartion for c/r; they
> > are followed by the actual c/r code.
> > 
> > Please apply to -mm, and let us know if there is any way we can
> > help.
> 
> Hi Andrew,
> 
> Oren sent v20 of the checkpoint/restart patchset out two weeks ago.
> We've addressed some feedback from linux-fsdevel and added network and
> pid namespace support.  So we could resend again now.  However we also
> have a bigger patchset in the works which is feature-neutral, but moves
> all the code out of linux-2.6/checkpoint/ and next to the code it
> affects.  I ancitipate #ifdef clashes though, so we'll
> need to do quite a bit of various-config-and-arch testing of the new
> code layout.  If you're at a good point to pull it, we can resend the
> code as is now so as to get some wider testing exposure. Or, if you prefer,
> we can wait until after the code move in case that would be seen as more
> amenable to meaningful review.
> 

I guess the final product would be better.  It sounds like it'll have
the added benefit of making the various interested parties pay more
attention, too ;)

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