From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH] Deny external checkpoint unless frozen
Date: Tue, 24 Feb 2009 10:38:07 -0800 [thread overview]
Message-ID: <1235500687.26788.260.camel@nimitz> (raw)
In-Reply-To: <20090224183116.GA21891-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Tue, 2009-02-24 at 12:31 -0600, Serge E. Hallyn wrote:
> Well the patch is mainly on top of your patchset which defines
> the string holding reasons for uncheckpointability, right? I
> assume you've modified that since then (too bad we're on a
> patch model at the moment) so seems easiest for you to toss it
> on top of your set.
>
> Or you can send your latest version and I (or Suka) can write
> the /proc/$$/checkpointable file.
What I have so far is actually only for fds and uses /proc/$$/fdinfo/*.
I haven't done the per-task file yet.
-- Dave
next prev parent reply other threads:[~2009-02-24 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 20:13 [PATCH] Deny external checkpoint unless frozen Sukadev Bhattiprolu
[not found] ` <20090221201317.GB13532-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-23 23:04 ` Serge E. Hallyn
[not found] ` <20090223230438.GA2590-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 0:39 ` Dave Hansen
2009-02-24 1:09 ` Serge E. Hallyn
[not found] ` <20090224010945.GA4797-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 1:18 ` Dave Hansen
2009-02-24 18:31 ` Serge E. Hallyn
[not found] ` <20090224183116.GA21891-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24 18:38 ` Dave Hansen [this message]
2009-03-18 7:31 ` Oren Laadan
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=1235500687.26788.260.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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