From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: cryo and mm->arg_start
Date: Fri, 11 Jul 2008 09:38:30 -0700 [thread overview]
Message-ID: <1215794310.9139.6.camel@nimitz> (raw)
In-Reply-To: <20080711131345.GA18870-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Fri, 2008-07-11 at 08:13 -0500, Serge E. Hallyn wrote:
>
> One thing we could do here is to start extending the cryo approach
> with Eric's checkpoint-as-a-coredump (caac?). We generate the
> tiniest of coredumps which, at first, contains nothing but
> mm->arg_start and maybe a process id. It would be simplest if
> it also contained a filename for the real executable,
The exec model sounds reasonable to me.
But, I think the filename of the exe is going to have to be in the
checkpoint *already*. It is mapped by at least one of the VMAs, and
will probably be dumped as a normal file-backed area.
Now, since arg_start is already set up at exec time, it doesn't seem
unreasonable to have the theoretical fs/binfmt_cr.c set it as well.
-- Dave
next prev parent reply other threads:[~2008-07-11 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 13:13 cryo and mm->arg_start Serge E. Hallyn
[not found] ` <20080711131345.GA18870-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-11 16:38 ` Dave Hansen [this message]
2008-07-11 21:26 ` Serge E. Hallyn
2008-07-11 22:01 ` Matt Helsley
[not found] ` <1215813673.5456.284.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-07-13 21:08 ` Serge E. Hallyn
[not found] ` <20080713210846.GD8186-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-15 21:40 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
[not found] ` <20080715214050.GA29648-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-16 15:23 ` Serge E. Hallyn
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=1215794310.9139.6.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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