From: andrea@suse.de
To: linux-mm@kvack.org
Subject: [PATCH 2 of 2] run panic the same way in both places
Date: Mon, 11 Jun 2007 16:30:41 +0200 [thread overview]
Message-ID: <dffa158c3b3c7849ffb0.1181572241@v2.random> (raw)
In-Reply-To: <patchbomb.1181572239@v2.random>
# HG changeset patch
# User Andrea Arcangeli <andrea@suse.de>
# Date 1181572232 -7200
# Node ID dffa158c3b3c7849ffb08ec0551ec999f50e2e59
# Parent aa5f6b86a146552d4b0c26b2aa5cc009a3093e49
run panic the same way in both places
The other panic is called after releasing some core global lock, that
sounds safe to have for both panics (just in case panic tries to do
anything more than oops does).
Signed-off-by: Andrea Arcangeli <andrea@suse.de>
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -428,8 +428,11 @@ void out_of_memory(struct zonelist *zone
last_tif_memdie_jiffies = jiffies;
}
- if (sysctl_panic_on_oom)
+ if (sysctl_panic_on_oom) {
+ read_unlock(&tasklist_lock);
+ cpuset_unlock();
panic("out of memory. panic_on_oom is selected\n");
+ }
retry:
/*
* Rambo mode: Shoot down a process and hope it solves whatever
@@ -437,7 +440,7 @@ retry:
*/
p = select_bad_process(&points);
/* Found nothing?!?! Either we hang forever, or we panic. */
- if (!p) {
+ if (unlikely(!p)) {
read_unlock(&tasklist_lock);
cpuset_unlock();
panic("Out of memory and no killable processes...\n");
--
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>
prev parent reply other threads:[~2007-06-11 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 14:30 [PATCH 0 of 2] oom incremental fixes andrea
2007-06-11 14:30 ` [PATCH 1 of 2] apply the anti deadlock features only to global oom andrea
2007-06-11 14:30 ` andrea [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=dffa158c3b3c7849ffb0.1181572241@v2.random \
--to=andrea@suse.de \
--cc=linux-mm@kvack.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