From: David Howells <dhowells@redhat.com>
To: npiggin@suse.de
Cc: dhowells@redhat.com, linux-arch@vger.kernel.org,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-am33-list@redhat.com
Subject: Re: [patch 09/14] mn10300: invoke oom-killer from page fault
Date: Fri, 23 Apr 2010 17:46:59 +0100 [thread overview]
Message-ID: <3369.1272041219@redhat.com> (raw)
In-Reply-To: <20100422161224.174904436@suse.de>
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: linux-am33-list@redhat.com
> Cc: David Howells <dhowells@redhat.com>
> Cc: linux-arch@vger.kernel.org
> Signed-off-by: Nick Piggin <npiggin@suse.de>
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2010-04-23 17:16 UTC|newest]
Thread overview: 49+ 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-22 20:46 ` David Rientjes
2010-04-26 20:32 ` 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
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-22 16:06 ` [patch 05/14] ia64: " npiggin
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 16:06 ` npiggin
2010-04-22 20:53 ` David Rientjes
2010-04-23 7:21 ` Geert Uytterhoeven
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-22 16:06 ` [patch 10/14] parisc: " npiggin
2010-04-22 16:06 ` npiggin
2010-04-22 20:56 ` David Rientjes
2010-04-22 20:56 ` David Rientjes
2010-04-26 15:00 ` Kyle McMartin
2010-04-26 15:00 ` Kyle McMartin
2010-04-22 16:06 ` [patch 11/14] powerpc: " npiggin
2010-04-22 21:44 ` David Rientjes
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-26 6:46 ` Paul Mundt
2010-04-22 16:06 ` [patch 14/14] xtensa: " npiggin
2010-04-22 20:58 ` David Rientjes
2010-04-23 16:46 ` [patch 04/14] frv: " David Howells
2010-04-23 16:46 ` David Howells [this message]
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=3369.1272041219@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=npiggin@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).