[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090723144753.GA12416@us.ibm.com>
Date: Thu, 23 Jul 2009 09:47:53 -0500
From: "Serge E. Hallyn" <serue@...ibm.com>
To: Oren Laadan <orenl@...rato.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...l.org>,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-api@...r.kernel.org, Dave Hansen <dave@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Pavel Emelyanov <xemul@...nvz.org>,
Alexey Dobriyan <adobriyan@...il.com>,
Oren Laadan <orenl@...columbia.edu>
Subject: Re: [RFC v17][PATCH 22/60] c/r: external checkpoint of a task
other than ourself
Quoting Oren Laadan (orenl@...rato.com):
> +/* setup checkpoint-specific parts of ctx */
> +static int init_checkpoint_ctx(struct ckpt_ctx *ctx, pid_t pid)
> +{
> + struct task_struct *task;
> + struct nsproxy *nsproxy;
> + int ret;
> +
> + /*
> + * No need for explicit cleanup here, because if an error
> + * occurs then ckpt_ctx_free() is eventually called.
> + */
> +
> + ctx->root_pid = pid;
> +
> + /* root task */
> + read_lock(&tasklist_lock);
> + task = find_task_by_vpid(pid);
> + if (task)
> + get_task_struct(task);
> + read_unlock(&tasklist_lock);
> + if (!task)
> + return -ESRCH;
> + else
> + ctx->root_task = task;
> +
> + /* root nsproxy */
> + rcu_read_lock();
> + nsproxy = task_nsproxy(task);
> + if (nsproxy)
> + get_nsproxy(nsproxy);
> + rcu_read_unlock();
> + if (!nsproxy)
> + return -ESRCH;
> + else
> + ctx->root_nsproxy = nsproxy;
> +
> + /* root freezer */
> + ctx->root_freezer = task;
> + geT_task_struct(task);
> +
> + ret = may_checkpoint_task(ctx, task);
> + if (ret) {
> + ckpt_write_err(ctx, NULL);
> + put_task_struct(task);
> + put_task_struct(task);
> + put_nsproxy(nsproxy);
I don't think this is safe - the ckpt_ctx_free() will
free them a second time because you're not setting them
to NULL, right?
> + return ret;
> + }
> +
> + return 0;
> +}
> +
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists