[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1236702165.10626.167.camel@nimitz>
Date: Tue, 10 Mar 2009 09:22:45 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Nathan Lynch <ntl@...ox.com>
Cc: Ingo Molnar <mingo@...e.hu>,
containers <containers@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [RFC][PATCH 00/11] track files for checkpointability
On Tue, 2009-03-10 at 10:57 -0500, Nathan Lynch wrote:
> From a0fb96aa41c4d360559013cfd7f32f07f449c1c4 Mon Sep 17 00:00:00 2001
> From: Nathan Lynch <ntl@...ox.com>
> Date: Mon, 9 Mar 2009 22:23:02 -0500
> Subject: [PATCH] checkpoint: make files_deny_checkpointing print task
> name and pid
>
> This lets the developer know *which* task performed an action that
> prevents checkpoint.
Can you think of any case where we wouldn't be calling
foo_deny_checkpoint() for a task other than current? Should we just use
current in the function directly instead of passing it in?
-- Dave
--
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