From: Nick Piggin <npiggin@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: linux-arch@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [patch 02/14] avr32: invoke oom-killer from page fault
Date: Fri, 23 Apr 2010 20:23:42 +1000 [thread overview]
Message-ID: <20100423102341.GB5683@laptop> (raw)
In-Reply-To: <alpine.DEB.2.00.1004221345350.25350@chino.kir.corp.google.com>
On Thu, Apr 22, 2010 at 01:45:56PM -0700, David Rientjes wrote:
> On Fri, 23 Apr 2010, npiggin@suse.de wrote:
>
> > As explained in commit 1c0fe6e3bd, we want to call the architecture independent
> > oom killer when getting an unexplained OOM from handle_mm_fault, rather than
> > simply killing current.
> >
> > Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
> > Cc: linux-arch@vger.kernel.org
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
> > ---
> > Index: linux-2.6/arch/avr32/mm/fault.c
> > ===================================================================
> > --- linux-2.6.orig/arch/avr32/mm/fault.c
> > +++ linux-2.6/arch/avr32/mm/fault.c
> > @@ -211,15 +211,10 @@ no_context:
> > */
> > out_of_memory:
> > up_read(&mm->mmap_sem);
> > - if (is_global_init(current)) {
> > - yield();
> > - down_read(&mm->mmap_sem);
> > - goto survive;
> > - }
> > - printk("VM: Killing process %s\n", tsk->comm);
> > - if (user_mode(regs))
> > - do_group_exit(SIGKILL);
> > - goto no_context;
> > + pagefault_out_of_memory();
> > + if (!user_mode(regs))
> > + goto no_context;
>
> We want to test for !user_mode(regs) before calling
> pagefault_out_of_memory().
Thanks for the careful review. We do indeed.
next prev parent reply other threads:[~2010-04-23 10:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 16:06 [patch 00/14] convert remaining architectures to pagefault_out_of_memory() npiggin
2010-04-22 16:06 ` [patch 01/14] alpha: invoke oom-killer from page fault npiggin
2010-04-22 20:46 ` David Rientjes
2010-04-26 20:32 ` David Rientjes
2010-04-28 2:58 ` Matt Turner
2010-04-28 3:30 ` Matt Turner
2010-04-22 16:06 ` [patch 02/14] avr32: " npiggin
2010-04-22 20:45 ` David Rientjes
2010-04-23 10:23 ` Nick Piggin [this message]
2010-04-22 16:06 ` [patch 03/14] cris: " npiggin
2010-04-22 20:50 ` David Rientjes
2010-04-23 4:33 ` Mikael Starvik
2010-04-22 16:06 ` [patch 04/14] frv: " npiggin
2010-04-22 20:50 ` David Rientjes
2010-04-23 16:46 ` David Howells
2010-04-22 16:06 ` [patch 05/14] ia64: " npiggin
2010-04-22 16:06 ` npiggin
2010-04-22 20:51 ` David Rientjes
2010-04-22 20:51 ` David Rientjes
2010-04-22 16:06 ` [patch 06/14] m32r: " npiggin
2010-04-22 20:52 ` David Rientjes
2010-04-22 16:06 ` [patch 07/14] m68k: " npiggin
2010-04-22 20:53 ` David Rientjes
2010-04-23 7:21 ` Geert Uytterhoeven
2010-04-22 16:06 ` [patch 08/14] microblaze: " npiggin
2010-04-22 20:54 ` David Rientjes
2010-04-23 6:30 ` Michal Simek
2010-04-22 16:06 ` [patch 09/14] mn10300: " npiggin
2010-04-23 16:46 ` David Howells
2010-04-22 16:06 ` [patch 10/14] parisc: " npiggin
2010-04-22 16:06 ` npiggin
2010-04-22 20:56 ` David Rientjes
2010-04-26 15:00 ` Kyle McMartin
2010-04-22 16:06 ` [patch 11/14] powerpc: " npiggin
2010-04-22 16:06 ` npiggin
2010-04-22 21:44 ` David Rientjes
2010-04-22 21:44 ` David Rientjes
2010-04-23 10:27 ` Nick Piggin
2010-04-23 10:27 ` Nick Piggin
2010-04-22 16:06 ` [patch 12/14] score: " npiggin
2010-04-22 20:57 ` David Rientjes
2010-04-28 7:30 ` liqin.chen
2010-04-22 16:06 ` [patch 13/14] sh: " npiggin
2010-04-22 16:06 ` npiggin
2010-04-22 20:58 ` David Rientjes
2010-04-22 20:58 ` David Rientjes
2010-04-26 6:46 ` Paul Mundt
2010-04-26 6:46 ` Paul Mundt
2010-04-22 16:06 ` [patch 14/14] xtensa: " npiggin
2010-04-22 20:58 ` David Rientjes
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=20100423102341.GB5683@laptop \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-arch@vger.kernel.org \
--cc=rientjes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.