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: [PATCH 6/6] Explain reason for task being uncheckpointable
Date: Tue, 17 Mar 2009 13:52:28 -0500 [thread overview]
Message-ID: <20090317185228.GC1039@us.ibm.com> (raw)
In-Reply-To: <20090317175149.GG10796-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Quoting Sukadev Bhattiprolu (sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
>
> From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> Date: Sat, 14 Mar 2009 10:21:07 -0700
> Subject: [PATCH 6/6] Explain reason for task being uncheckpointable
>
> Try to give an useful message on why a task is uncheckpointable.
As I said somewhere else, I think this is what makes it worth
having a procfile (or debugfs file) over just doing a trial
sys_checkpoint() with an invalid fd.
However,
> Signed-off-by: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> ---
> checkpoint/checkpoint.c | 13 +++++++++----
> fs/proc/base.c | 19 ++++++++++++++++++-
> include/linux/checkpoint.h | 7 +++++++
> 3 files changed, 34 insertions(+), 5 deletions(-)
>
> diff --git a/checkpoint/checkpoint.c b/checkpoint/checkpoint.c
> index ad0956c..c8c377d 100644
> --- a/checkpoint/checkpoint.c
> +++ b/checkpoint/checkpoint.c
> @@ -264,18 +264,23 @@ static int cr_write_all_tasks(struct cr_ctx *ctx)
> return ret;
> }
>
> -int task_checkpointable(struct task_struct *t)
> +int __task_checkpointable(struct task_struct *t)
> {
> if (t->state == TASK_DEAD) {
> pr_warning("c/r: task %d is TASK_DEAD\n", task_pid_vnr(t));
> - return 0;
> + return CR_DEAD;
> }
>
> /* Verify that task is frozen, unless it is self-checkpoint */
> if (t != current && !frozen(t))
> - return 0;
> + return CR_NOT_FROZEN;
> +
> + return CR_CHECKPOINTABLE;
> +}
>
> - return 1;
> +int task_checkpointable(struct task_struct *t)
> +{
> + return __task_checkpointable(t) == CR_CHECKPOINTABLE;
> }
>
> static int cr_may_checkpoint_task(struct task_struct *t, struct cr_ctx *ctx)
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index 989ca93..6e4c07c 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -2502,9 +2502,26 @@ static int proc_pid_personality(struct seq_file *m, struct pid_namespace *ns,
> }
>
> #ifdef CONFIG_CHECKPOINT_RESTART
> +static char *explain_checkpointable(int reason)
> +{
> + char *message;
> +
> + switch(reason) {
> + case CR_CHECKPOINTABLE: message = "1"; break;
> + case CR_DEAD: message = "0 (dead)"; break;
> + case CR_NOT_FROZEN: message = "0 (not frozen)"; break;
> + default: message = "0 (unknown)"; break;
I don't think splitting it up this way is going to work long-term.
It means you need one code for each type of message, and can't give
any more detail beyond that (i.e. the value of
current->nsproxy->uts_ns.refcount, or whatever).
I think it would be better to pass a buffer into __task_checkpointable,
and let task_checkpointable() pass in a NULL buffer meaning "I
(sys_checkpoint) don't care about the explanation".
> + }
> + return message;
> +}
> +
> static int proc_pid_checkpointable(struct task_struct *task, char *buffer)
> {
> - return sprintf(buffer, "%d\n", task_checkpointable(task));
> + int rc;
> +
> + rc = __task_checkpointable(task);
> +
> + return scnprintf(buffer, PAGE_SIZE, "%s\n", explain_checkpointable(rc));
> }
> #endif
>
> diff --git a/include/linux/checkpoint.h b/include/linux/checkpoint.h
> index d1f53a6..a1eba73 100644
> --- a/include/linux/checkpoint.h
> +++ b/include/linux/checkpoint.h
> @@ -142,6 +142,13 @@ static inline int cr_enabled(void)
> return 1;
> }
>
> +enum cr_uncheckpointable_reason {
> + CR_CHECKPOINTABLE = 0,
> + CR_DEAD,
> + CR_NOT_FROZEN
> +};
> +
> +int __task_checkpointable(struct task_struct *t);
> int task_checkpointable(struct task_struct *t);
>
> #else /* !CONFIG_CHECKPOINT_RESTART */
> --
> 1.5.2.5
>
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2009-03-17 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 17:43 [PATCH 0/6] /proc/pid/checkpointable Sukadev Bhattiprolu
[not found] ` <20090317174359.GA10796-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-17 17:49 ` [PATCH 1/6] Checkpoint multiple processes Sukadev Bhattiprolu
2009-03-17 17:49 ` [PATCH 2/6] Restart " Sukadev Bhattiprolu
2009-03-17 17:50 ` [PATCH 3/6] Check 'may_checkpoint()' early Sukadev Bhattiprolu
[not found] ` <20090317175013.GD10796-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-26 5:58 ` Sukadev Bhattiprolu
[not found] ` <20090326055840.GA8220-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-26 13:25 ` Serge E. Hallyn
2009-03-17 17:50 ` [PATCH 4/6] Deny external checkpoint unless task is frozen Sukadev Bhattiprolu
2009-03-17 17:51 ` [PATCH 5/6] Define and use proc_pid_checkpointable() Sukadev Bhattiprolu
2009-03-17 17:51 ` [PATCH 6/6] Explain reason for task being uncheckpointable Sukadev Bhattiprolu
[not found] ` <20090317175149.GG10796-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-17 18:52 ` Serge E. Hallyn [this message]
[not found] ` <20090317185228.GC1039-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-18 6:50 ` Sukadev Bhattiprolu
2009-03-18 9:28 ` [PATCH 0/6] /proc/pid/checkpointable 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=20090317185228.GC1039@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 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.