From: Nick Piggin <npiggin@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Jeff Dike <jdike@addtoit.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] oom: OOM-Killed process don't invoke pagefault-oom
Date: Fri, 15 Jan 2010 00:02:57 +1100 [thread overview]
Message-ID: <20100114130257.GB8381@laptop> (raw)
In-Reply-To: <20100114191940.6749.A69D9226@jp.fujitsu.com>
Hi,
I don't think this should be required, because the oom killer does not
kill a new task if there is already one in memdie state.
If you have any further tweaks to the heuristic (such as a fatal signal
pending), then it should probably go in select_bad_process() or
somewhere like that.
Thanks,
Nick
On Thu, Jan 14, 2010 at 07:22:34PM +0900, KOSAKI Motohiro wrote:
>
> Nick, I've found this issue by code review. I'm glad if you review this
> patch.
>
> Thanks.
>
> =============================
> commit 1c0fe6e3 (invoke oom-killer from page fault) created
> page fault specific oom handler.
>
> But If OOM occur, alloc_pages() in page fault might return
> NULL. It mean page fault return VM_FAULT_OOM. But OOM Killer
> itself sholdn't invoke next OOM Kill. it is obviously strange.
>
> Plus, process exiting itself makes some free memory. we
> don't need kill another process.
>
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Cc: Nick Piggin <npiggin@suse.de>
> Cc: Jeff Dike <jdike@addtoit.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> mm/oom_kill.c | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 4f167b8..86cecdf 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -596,6 +596,15 @@ void pagefault_out_of_memory(void)
> {
> unsigned long freed = 0;
>
> + /*
> + * If the task was received SIGKILL while memory allocation, alloc_pages
> + * might return NULL and it cause page fault return VM_FAULT_OOM. But
> + * in such case, the task don't need kill any another task, it need
> + * just die.
> + */
> + if (fatal_signal_pending(current))
> + return;
> +
> blocking_notifier_call_chain(&oom_notify_list, 0, &freed);
> if (freed > 0)
> /* Got some memory back in the last second. */
> --
> 1.6.5.2
>
>
--
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:[~2010-01-14 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 10:22 KOSAKI Motohiro
2010-01-14 13:02 ` Nick Piggin [this message]
2010-01-15 6:21 ` KOSAKI Motohiro
2010-01-18 7:29 ` Nick Piggin
2010-01-18 8:21 ` 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=20100114130257.GB8381@laptop \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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