From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Subject: c/r updates
Date: Thu, 14 May 2009 11:53:40 -0400 [thread overview]
Message-ID: <4A0C3E84.1040702@cs.columbia.edu> (raw)
Hi,
The current development kernel git:
git://git.ncl.cs.columbia.edu/pub/git/linux-cr [ckpt-v15-dev]
The current development user tools git:
git://git.ncl.cs.columbia.edu/pub/git/user-cr [ckpt-v15-dev]
(branch naming will remain consistent from now ...)
Dave: I pushed a series of patches/fixes to current c/r tree, some of
which are are relevant to the patch series you're preparing.
Nathan: patches "tee...", "splice..." and "c/r: redo..." change the
way pipes are saved/restored, and avoids the lockdep issue.
Patches:
c/r: fix ckpt_obj_fetch return values (v3)
c/r: redo {checkpoint,restore}_pipe() using splice and tee
splice: added support for pipe-to-pipe splice()
tee: don't return 0 when another task drains/fills a pipe
c/r: fix incorrect 'cond ? : xxx' statemnt
c/r: set expire value to zero for restart block that expired
c/r: x86 checkpoint support does not depend on CONFIG_COMPAT_VDSO
c/r: s390: remove unused variable ret
c/r: s390: fix unterminated ifdef
c/r: test for ops->restore method in do_restore_file()
c/r: grab missing reference to a (pipe) file if not first encounter
Separate restore of task nxproxy (first) and memory (second)
Fix leak of objects restored in restore_obj()
c/r: fix users count of files that are pointed to by mm->exe_file
c/r: fix incorrect variable type in call to strict_strtoul()
Oren.
next reply other threads:[~2009-05-14 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 15:53 Oren Laadan [this message]
[not found] ` <4A0C3E84.1040702-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-05-14 16:26 ` c/r updates Nathan Lynch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0C3E84.1040702@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox