From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: [PATCH user-cr] fix sid swap buglet
Date: Thu, 5 Nov 2009 17:24:36 -0600 [thread overview]
Message-ID: <20091105232436.GA301@us.ibm.com> (raw)
In the case of a restart of a subtree checkpoint, some sids
may be recorded as 0. If so, then we substitute the coordinator's
sid. The code to do that wasn't quite right, and in fact writes
past the end of the pids_arr, which happens to be into the
copy_arr. As a result, the kernel was getting bogus data for
substituted pids. In my own case that lead to sys_restart()
waiting on a bogus vpid (in particular, the pid of my bash shell).
Fix that.
Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
---
restart.c | 22 ++++++++++++----------
1 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/restart.c b/restart.c
index 20f5055..f0b7862 100644
--- a/restart.c
+++ b/restart.c
@@ -2029,17 +2029,19 @@ static int ckpt_adjust_pids(struct ckpt_ctx *ctx)
if (ctx->pids_arr[m].vpgid == swap.old)
ctx->copy_arr[m].vpgid = swap.new;
}
+ }
- /*
- * If the task's {sid,pgid} was zeroed out (inside
- * ckpt_init_tree) then substitute the coordinator's
- * sid for it now. (This should leave no more 0's in
- * restart of a subtree-checkpoint).
- */
- if (ctx->tasks_arr[n].flags & TASK_ZERO_SID)
- ctx->pids_arr[m].vsid = coord_sid;
- if (ctx->tasks_arr[n].flags & TASK_ZERO_PGID)
- ctx->pids_arr[m].vpgid = coord_sid;
+ /*
+ * If the task's {sid,pgid} was zeroed out (inside
+ * ckpt_init_tree) then substitute the coordinator's
+ * sid for it now. (This should leave no more 0's in
+ * restart of a subtree-checkpoint).
+ */
+ for (m = 0; m < ctx->pids_nr; m++) {
+ if (ctx->tasks_arr[m].flags & TASK_ZERO_SID)
+ ctx->copy_arr[m].vsid = coord_sid;
+ if (ctx->tasks_arr[m].flags & TASK_ZERO_PGID)
+ ctx->copy_arr[m].vpgid = coord_sid;
}
memcpy(ctx->pids_arr, ctx->copy_arr, len);
--
1.6.1.1
next reply other threads:[~2009-11-05 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 23:24 Serge E. Hallyn [this message]
[not found] ` <20091105232436.GA301-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-11-05 23:43 ` [PATCH user-cr] fix sid swap buglet 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=20091105232436.GA301@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=orenl-eQaUEPhvms7ENvBUuze7eA@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 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.