linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Rik van Riel <riel@redhat.com>, Oleg Nesterov <oleg@redhat.com>,
	linux-mm <linux-mm@kvack.org>, Andrey Vagin <avagin@openvz.org>,
	Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 5/5] x86,mm: make pagefault killable
Date: Wed, 23 Mar 2011 17:09:59 +0900 (JST)	[thread overview]
Message-ID: <20110323171051.1ADA.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110323164949.5be6aa48.kamezawa.hiroyu@jp.fujitsu.com>

> On Tue, 22 Mar 2011 20:09:29 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> 
> > When oom killer occured, almost processes are getting stuck following
> > two points.
> > 
> > 	1) __alloc_pages_nodemask
> > 	2) __lock_page_or_retry
> > 
> > 1) is not much problematic because TIF_MEMDIE lead to make allocation
> > failure and get out from page allocator. 2) is more problematic. When
> > OOM situation, Zones typically don't have page cache at all and Memory
> > starvation might lead to reduce IO performance largely. When fork bomb
> > occur, TIF_MEMDIE task don't die quickly mean fork bomb may create
> > new process quickly rather than oom-killer kill it. Then, the system
> > may become livelock.
> > 
> > This patch makes pagefault interruptible by SIGKILL.
> > 
> > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > ---
> >  arch/x86/mm/fault.c |    9 +++++++++
> >  include/linux/mm.h  |    1 +
> >  mm/filemap.c        |   22 +++++++++++++++++-----
> >  3 files changed, 27 insertions(+), 5 deletions(-)
> > 
> > diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
> > index 20e3f87..797c7d0 100644
> > --- a/arch/x86/mm/fault.c
> > +++ b/arch/x86/mm/fault.c
> > @@ -1035,6 +1035,7 @@ do_page_fault(struct pt_regs *regs, unsigned long error_code)
> >  	if (user_mode_vm(regs)) {
> >  		local_irq_enable();
> >  		error_code |= PF_USER;
> > +		flags |= FAULT_FLAG_KILLABLE;
> >  	} else {
> >  		if (regs->flags & X86_EFLAGS_IF)
> >  			local_irq_enable();
> > @@ -1138,6 +1139,14 @@ good_area:
> >  	}
> >  
> >  	/*
> > +	 * Pagefault was interrupted by SIGKILL. We have no reason to
> > +	 * continue pagefault.
> > +	 */
> > +	if ((flags & FAULT_FLAG_KILLABLE) && (fault & VM_FAULT_RETRY) &&
> > +	    fatal_signal_pending(current))
> > +		return;
> > +
> 
> Hmm? up_read(&mm->mmap_sem) ?

When __lock_page_or_retry() return 0, It call up_read(mmap_sem) in this
function.

I agree this is strange (or ugly). but I don't want change this spec in
this time.



--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-03-23  8:10 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110314232156.0c363813.akpm@linux-foundation.org>
     [not found] ` <20110315153801.3526.A69D9226@jp.fujitsu.com>
2011-03-22 11:04   ` [patch 0/5] oom: a few anti fork bomb patches KOSAKI Motohiro
2011-03-22 11:05     ` [PATCH 1/5] vmscan: remove all_unreclaimable check from direct reclaim path completely KOSAKI Motohiro
2011-03-22 14:49       ` Minchan Kim
2011-03-23  5:21         ` KOSAKI Motohiro
2011-03-23  6:59           ` Minchan Kim
2011-03-23  7:13             ` KOSAKI Motohiro
2011-03-23  8:24               ` Minchan Kim
2011-03-23  8:44                 ` KOSAKI Motohiro
2011-03-23  9:02                   ` Minchan Kim
2011-03-24  2:11                     ` KOSAKI Motohiro
2011-03-24  2:21                       ` Andrew Morton
2011-03-24  2:48                         ` KOSAKI Motohiro
2011-03-24  3:04                           ` Andrew Morton
2011-03-24  5:35                             ` KOSAKI Motohiro
2011-03-24  4:19                       ` Minchan Kim
2011-03-24  5:35                         ` KOSAKI Motohiro
2011-03-24  5:53                           ` Minchan Kim
2011-03-24  6:16                             ` KOSAKI Motohiro
2011-03-24  6:32                               ` Minchan Kim
2011-03-24  7:03                                 ` KOSAKI Motohiro
2011-03-24  7:25                                   ` Minchan Kim
2011-03-24  7:28                                     ` KOSAKI Motohiro
2011-03-24  7:34                                       ` Minchan Kim
2011-03-24  7:41                                         ` Minchan Kim
2011-03-24  7:43                                         ` KOSAKI Motohiro
2011-03-24  7:43                           ` Minchan Kim
2011-03-23  7:41       ` KAMEZAWA Hiroyuki
2011-03-23  7:55         ` KOSAKI Motohiro
2011-03-22 11:06     ` [PATCH 2/5] Revert "oom: give the dying task a higher priority" KOSAKI Motohiro
2011-03-23  7:42       ` KAMEZAWA Hiroyuki
2011-03-23 13:40         ` Luis Claudio R. Goncalves
2011-03-24  0:06           ` KOSAKI Motohiro
2011-03-24 15:27       ` Minchan Kim
2011-03-28  9:48         ` KOSAKI Motohiro
2011-03-28 12:28           ` Minchan Kim
2011-03-28  9:51         ` Peter Zijlstra
2011-03-28 12:21           ` Minchan Kim
2011-03-28 12:28             ` Peter Zijlstra
2011-03-28 12:40               ` Minchan Kim
2011-03-28 13:10                 ` Luis Claudio R. Goncalves
2011-03-28 13:18                   ` Peter Zijlstra
2011-03-28 13:56                     ` Luis Claudio R. Goncalves
2011-03-29  2:46                     ` KOSAKI Motohiro
2011-03-28 13:48                   ` Minchan Kim
2011-03-22 11:08     ` [PATCH 3/5] oom: create oom autogroup KOSAKI Motohiro
2011-03-22 23:21       ` Minchan Kim
2011-03-23  1:27         ` KOSAKI Motohiro
2011-03-23  2:41           ` Mike Galbraith
2011-03-22 11:08     ` [PATCH 4/5] mm: introduce wait_on_page_locked_killable KOSAKI Motohiro
2011-03-23  7:44       ` KAMEZAWA Hiroyuki
2011-03-24 15:04       ` Minchan Kim
2011-03-22 11:09     ` [PATCH 5/5] x86,mm: make pagefault killable KOSAKI Motohiro
2011-03-23  7:49       ` KAMEZAWA Hiroyuki
2011-03-23  8:09         ` KOSAKI Motohiro [this message]
2011-03-23 14:34           ` Linus Torvalds
2011-03-24 15:10       ` Minchan Kim
2011-03-24 17:13       ` Oleg Nesterov
2011-03-24 17:34         ` Linus Torvalds
2011-03-28  7:00           ` KOSAKI Motohiro

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=20110323171051.1ADA.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=hughd@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.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