Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	"David C. Hansen"
	<haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC][PATCH] Check may_checkpoint() early
Date: Mon, 23 Feb 2009 19:06:34 -0600	[thread overview]
Message-ID: <20090224010634.GC2590@us.ibm.com> (raw)
In-Reply-To: <20090221201221.GA13532-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

Quoting Sukadev Bhattiprolu (sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> 
> From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> Date: Mon, 16 Feb 2009 12:05:50 -0800
> Subject: [PATCH] Check 'may_checkpoint()' early
> 
> We currently check if a task is checkpointable when writing the task
> information to checkpoint file. The small downside of doing this check
> late is that we may have processed several processes in the tree before
> hitting one that cannot be checkpointed.
> 
> We anyway walk the process tree we are checkpointing earlier, while
> counting the tasks. We could check if all processes in the tree are
> checkpointable at that time and fail early if any of them are not.
> Since the process tree should be frozen, checking earlier should not
> matter ?
> 
> For now, the patch leaves the existing check in cr_write_pids(). We

Yes we'll at least need to add checks that there is no running task
sharing an mm or files_struct with a checkpointed task, else some of
our checks will definately be racy (and are even now).

> can remove that later.
> 
> Signed-off-by: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> ---
>  checkpoint/checkpoint.c |    9 +++++++++
>  1 files changed, 9 insertions(+), 0 deletions(-)
> 
> diff --git a/checkpoint/checkpoint.c b/checkpoint/checkpoint.c
> index 64155de..2bbb409 100644
> --- a/checkpoint/checkpoint.c
> +++ b/checkpoint/checkpoint.c
> @@ -347,11 +347,18 @@ static int cr_tree_count_tasks(struct cr_ctx *ctx)
>  	struct task_struct **tasks_arr = ctx->tasks_arr;
>  	int tasks_nr = ctx->tasks_nr;
>  	int nr = 0;
> +	int ret;
> 
>  	read_lock(&tasklist_lock);
> 
>  	/* count tasks via DFS scan of the tree */
>  	while (1) {
> +		ret = cr_may_checkpoint_task(task, ctx);
> +		if (ret < 0) {
> +			nr = ret;
> +			break;
> +		}
> +
>  		if (tasks_arr) {
>  			/* unlikely... but if so then try again later */
>  			if (nr == tasks_nr) {
> @@ -409,6 +416,8 @@ static int cr_build_tree(struct cr_ctx *ctx)
> 
>  	/* count tasks (no side effects) */
>  	n = cr_tree_count_tasks(ctx);
> +	if (n < 0)
> +		return n;
> 
>  	ctx->tasks_nr = n;
>  	ctx->tasks_arr = kzalloc(n * sizeof(*ctx->tasks_arr), GFP_KERNEL);
> -- 
> 1.5.2.5

      parent reply	other threads:[~2009-02-24  1:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 20:12 [RFC][PATCH] Check may_checkpoint() early Sukadev Bhattiprolu
     [not found] ` <20090221201221.GA13532-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-02-24  1:06   ` Serge E. Hallyn [this message]

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=20090224010634.GC2590@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=haveblue-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