From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Glauber Costa <glommer@parallels.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, Andrew Vagin <avagin@parallels.com>,
Pavel Emelyanov <xemul@parallels.com>,
James Bottomley <jbottomley@parallels.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Dave Hansen <dave@linux.vnet.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [patch 5/5] elf: Add support for loading ET_CKPT files
Date: Fri, 21 Oct 2011 15:20:31 +0400 [thread overview]
Message-ID: <20111021112031.GO14464@moon> (raw)
In-Reply-To: <4EA15224.10102@parallels.com>
On Fri, Oct 21, 2011 at 03:06:12PM +0400, Glauber Costa wrote:
...
> exec() is a fundamental interface to the kernel, and the change
> proposed here is too disruptive. Not only that, it is rather
> unannounced: since not always one knows kind of fmt file is being
> exec'd, it gets hard to infer which behavior to expect.
>
This missed snipped in changelog indeed my very fault, sorry for that.
> I am wondering, though: if exec is a problem, but the binary handler
> is not, maybe we can exec a process using this handler, and then
> have the handler itself to create the thread hierarchy. This way we
> avoid changing exec() behavior at all, yet achieving the same
> results.
>
> What do you think?
>
>
Glauber, could you please elaborate, you mean to call for forks inside
elf-chkpt handler, right? Or you mean something else?
Cyrill
next prev parent reply other threads:[~2011-10-21 11:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:04 [patch 0/5] [RFC] Checkpoint/restore and Elf extension Cyrill Gorcunov
2011-10-14 11:04 ` [patch 1/5] proc: Introduce the Children: line in /proc/<pid>/status Cyrill Gorcunov
2011-10-14 16:36 ` Tejun Heo
2011-10-14 11:04 ` [patch 2/5] fs: Add do_close helper Cyrill Gorcunov
2011-10-14 11:04 ` [patch 3/5] fs, proc: Add /proc/$pid/tls entry Cyrill Gorcunov
2011-10-14 16:40 ` Tejun Heo
2011-10-14 16:43 ` Cyrill Gorcunov
2011-10-14 11:04 ` [patch 4/5] fs, proc: Add start_data, end_data, start_brk members to /proc/$pid/stat Cyrill Gorcunov
2011-10-14 11:04 ` [patch 5/5] elf: Add support for loading ET_CKPT files Cyrill Gorcunov
2011-10-14 17:10 ` Tejun Heo
2011-10-14 17:33 ` Tejun Heo
2011-10-19 9:03 ` Pavel Emelyanov
2011-10-19 18:22 ` Tejun Heo
2011-10-19 18:49 ` Cyrill Gorcunov
2011-10-19 18:52 ` Cyrill Gorcunov
2011-10-19 18:53 ` Tejun Heo
2011-10-19 19:56 ` Cyrill Gorcunov
2011-10-21 18:26 ` Tejun Heo
2011-10-21 18:36 ` Cyrill Gorcunov
2011-10-21 18:42 ` Cyrill Gorcunov
2011-10-21 18:48 ` Tejun Heo
2011-10-21 18:53 ` Cyrill Gorcunov
2011-10-22 6:34 ` Pavel Emelyanov
2011-10-20 8:33 ` Pavel Emelyanov
2011-10-20 15:56 ` Tejun Heo
2011-10-20 16:04 ` Cyrill Gorcunov
2011-10-20 17:30 ` Pavel Emelyanov
2011-10-15 18:59 ` Cyrill Gorcunov
2011-10-21 11:06 ` Glauber Costa
2011-10-21 11:20 ` Cyrill Gorcunov [this message]
2011-10-21 11:21 ` Glauber Costa
2011-10-21 11:35 ` Cyrill Gorcunov
2011-10-22 16:49 ` Dan Merillat
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=20111021112031.GO14464@moon \
--to=gorcunov@gmail.com \
--cc=adobriyan@gmail.com \
--cc=avagin@parallels.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=glommer@parallels.com \
--cc=hpa@zytor.com \
--cc=jbottomley@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xemul@parallels.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.