[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1227605300.1566.17.camel@penberg-laptop>
Date: Tue, 25 Nov 2008 11:28:20 +0200
From: Pekka Enberg <penberg@...helsinki.fi>
To: Ying Han <yinghan@...gle.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Paul Menage <menage@...gle.com>,
David Rientjes <rientjes@...gle.com>,
Rohit Seth <rohitseth@...gle.com>,
akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH][V4]Make get_user_pages interruptible
On Mon, 2008-11-24 at 15:21 -0800, Ying Han wrote:
> From: Ying Han <yinghan@...gle.com>
>
> make get_user_pages interruptible
> The initial implementation of checking TIF_MEMDIE covers the cases of OOM
> killing. If the process has been OOM killed, the TIF_MEMDIE is set and it
> return immediately. This patch includes:
>
> 1. add the case that the SIGKILL is sent by user processes. The process can
> try to get_user_pages() unlimited memory even if a user process has sent a
> SIGKILL to it(maybe a monitor find the process exceed its memory limit and
> try to kill it). In the old implementation, the SIGKILL won't be handled
> until the get_user_pages() returns.
>
> 2. change the return value to be ERESTARTSYS. It makes no sense to return
> ENOMEM if the get_user_pages returned by getting a SIGKILL signal.
> Considering the general convention for a system call interrupted by a
> signal is ERESTARTNOSYS, so the current return value is consistant to that.
Looks good to me (but I'm not the maintainer of this particular piece of
code).
Acked-by: Pekka Enberg <penberg@...helsinki.fi>
You might want to add an explanation why we check both 'tsk' and
'current' in either in the patch description or as a comment, though. Or
just add a link to the mailing list archives in the description or
something.
> Signed-off-by: Paul Menage <menage@...gle.com>
> Singed-off-by: Ying Han <yinghan@...gle.com>
^^^^^^
I'm sure you have a beautiful singing voice but from legal point of
view, it's probably better to just sign it off. ;-)
Pekka
--
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