From: David Rientjes <rientjes@google.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-mm@kvack.org
Subject: Re: [patch] mm, oom: do not schedule if current has been killed
Date: Mon, 18 Jun 2012 19:23:21 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1206181918390.13293@chino.kir.corp.google.com> (raw)
In-Reply-To: <4FDFDCA7.8060607@jp.fujitsu.com>
On Tue, 19 Jun 2012, Kamezawa Hiroyuki wrote:
> fatal_signal_pending() == false if test_thread_flag(TIF_MEMDIE)==false ?
>
Yeah, the only thing that sets TIF_MEMDIE is the oom killer and it
immediately SIGKILLs it afterwards.
Aside: I've been thinking of adding a check to the page allocator for
!(gfp & __GFP_FS) && !(gfp & __GFP_NORETRY) to set TIF_MEMDIE for current
if it has a fatal signal since such an allocation isn't eligible for
calling into the oom killer.
--
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:[~2012-06-19 2:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 1:08 David Rientjes
2012-06-19 1:57 ` Kamezawa Hiroyuki
2012-06-19 2:23 ` David Rientjes [this message]
2012-06-19 2:31 ` [patch v2] " David Rientjes
2012-06-19 2:51 ` Kamezawa Hiroyuki
2012-06-19 6:03 ` KOSAKI Motohiro
2012-06-19 6:26 ` David Rientjes
2012-06-19 17:32 ` KOSAKI Motohiro
2012-06-19 18:59 ` David Rientjes
2012-06-19 19:29 ` KOSAKI Motohiro
2012-06-19 13:55 ` Oleg Nesterov
2012-06-19 20:24 ` David Rientjes
2012-06-19 20:58 ` [patch v3] " David Rientjes
2012-06-19 21:39 ` KOSAKI Motohiro
2012-06-20 0:38 ` Kamezawa Hiroyuki
2012-06-21 1:23 ` 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=alpine.DEB.2.00.1206181918390.13293@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.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