Linux Container Development
 help / color / mirror / Atom feed
From: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 1/1] checkpoint: Note checkpointability of mm_struct (v2)
Date: Wed, 04 Mar 2009 14:01:23 -0800	[thread overview]
Message-ID: <87iqmpvtfw.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: 20090302161115.GA10484@us.ibm.com

SH> +static inline void task_show_checkpointable(struct seq_file *m,
SH> +						struct task_struct *p)
SH> +{
SH> +	if (test_bit(0, &p->mm->may_checkpoint))
SH> +		seq_printf(m,	"mm is checkpointable\n");
                             ^^^
You have a hard tab in the middle of the line.  Was that intentional?

SH> +	else
SH> +		seq_printf(m,	"mm is not checkpointable\n");
SH> +
SH> +	if (test_bit(0, &p->files->may_checkpoint))
SH> +		seq_printf(m,	"files are checkpointable\n");
SH> +	else
SH> +		seq_printf(m,	"files are not checkpointable\n");
SH> +}

These too.

SH> +static inline void __mm_deny_checkpointing(struct mm_struct *mm,
SH> +		char *file, int line)
SH> +{
SH> +	if (!test_and_clear_bit(0, &mm->may_checkpoint))
SH> +		return;
SH> +	printk(KERN_INFO "process performed an (mm) action that can not be "
SH> +			"checkpointed at: %s:%d\n", file, line);
SH> +}
SH> +#define mm_deny_checkpointing(f) \
SH> +	__mm_deny_checkpointing(f, __FILE__, __LINE__)

There is no definition of mm_deny_checkpointing() outside of
CONFIG_CHECKPOINT_RESTART, which means that you get a build error
because mm->may_checkpoint is only present when CR is enabled.

SH> -	WARN_ON(1);
SH> +	//WARN_ON(1);

I assume commenting this out wasn't intended to be in this patch.

-- 
Dan Smith
IBM Linux Technology Center
email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org

  reply	other threads:[~2009-03-04 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 16:11 [PATCH 1/1] checkpoint: Note checkpointability of mm_struct (v2) Serge E. Hallyn
2009-03-04 22:01 ` Dan Smith [this message]
     [not found]   ` <87iqmpvtfw.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-03-04 22:35     ` Serge E. Hallyn
     [not found]       ` <20090304223505.GA27248-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-04 22:44         ` Dave Hansen

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=87iqmpvtfw.fsf@caffeine.danplanet.com \
    --to=danms-r/jw6+rmf7hqt0dzr+alfa@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