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>,
Nadia Derbey <Nadia.Derbey-6ktuUTfB/bM@public.gmane.org>
Subject: Re: restarting tests/sleep
Date: Mon, 09 Jun 2008 09:32:28 -0700 [thread overview]
Message-ID: <1213029148.3508.25.camel@nimitz> (raw)
In-Reply-To: <20080609162309.GA32120-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
On Mon, 2008-06-09 at 11:23 -0500, Serge E. Hallyn wrote:
>
>
> Yeah that's insurmountable - notice the stack in the process which was
> fork()ed to be the restarted process topped at bfcab000, while the
> checkpointed stack topped at bfdae000. You're not allowed to write
> above the stack. So the only things to do are
>
> 1. keep trying the restart in the hopes you get a task with
> stack topping at or above bfdae000
> 2. if the checkpointed stack is too high to be likely to be
> restartable, generate a new checkpoint image and you
> should get a lower stack top.
>
> (Dave, maybe you had other ideas I haven't considered)
Have you tried turning of stack randomization? It should make the stack
more dependable at exec. We could also provide a hint somewhere on
exec() where to place the stack.
-- Dave
next prev parent reply other threads:[~2008-06-09 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <484D2E7C.4060905@bull.net>
[not found] ` <20080609143626.GA23253@us.ibm.com>
[not found] ` <484D4364.2080509@bull.net>
[not found] ` <484D4364.2080509-6ktuUTfB/bM@public.gmane.org>
2008-06-09 16:23 ` restarting tests/sleep Serge E. Hallyn
[not found] ` <20080609162309.GA32120-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-06-09 16:32 ` Dave Hansen [this message]
2008-06-09 18:19 ` 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=1213029148.3508.25.camel@nimitz \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=Nadia.Derbey-6ktuUTfB/bM@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