From: Pekka Enberg <penberg@cs.helsinki.fi>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Ying Han <yinghan@google.com>, linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Oleg Nesterov <oleg@redhat.com>, Paul Menage <menage@google.com>,
Rohit Seth <rohitseth@google.com>
Subject: Re: [PATCH][V7]make get_user_pages interruptible
Date: Wed, 03 Dec 2008 10:21:48 +0200 [thread overview]
Message-ID: <1228292508.22472.14.camel@penberg-laptop> (raw)
In-Reply-To: <20081203161834.1D4A.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Wed, 2008-12-03 at 16:19 +0900, KOSAKI Motohiro wrote:
> > From: Ying Han <yinghan@google.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.
> >
> > Signed-off-by: Paul Menage <menage@google.com>
> > Signed-off-by: Ying Han <yinghan@google.com>
>
> looks good to me.
>
> Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Looks good to me too.
Reviewed-by: Pekka Enberg <penberg@cs.helsinki.fi>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-03 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 5:17 Ying Han
2008-12-03 7:19 ` KOSAKI Motohiro
2008-12-03 8:21 ` Pekka Enberg [this message]
2008-12-03 15:03 ` Lee Schermerhorn
2008-12-03 20:25 ` Ying Han
2008-12-03 20:36 ` Lee Schermerhorn
2008-12-03 20:01 ` [PATCH] mmotm: ignore sigkill in get_user_pages during munlock Lee Schermerhorn
2008-12-04 0:30 ` KOSAKI Motohiro
2008-12-04 1:19 ` Ying Han
2008-12-04 1:49 ` Lee Schermerhorn
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=1228292508.22472.14.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=oleg@redhat.com \
--cc=rohitseth@google.com \
--cc=yinghan@google.com \
/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