From: Michal Hocko <mhocko@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] oom: sysrq+f shouldn't not panic the system + cleanup
Date: Thu, 18 Jun 2015 11:57:25 +0200 [thread overview]
Message-ID: <1434621447-21175-1-git-send-email-mhocko@suse.cz> (raw)
Hi,
I have split the patch sent previously http://marc.info/?l=linux-mm&m=143323521519798&w=2
into two parts. The first patch prevents from the panic when OOM
killer is sysrq triggered. This is an obvious bug fix and hopefuly not
controversial.
I still believe that combining the regular and the sysrq triggered OOM
paths is ugly, error prone and it deserves a split up which is done in
the second patch. There are no functional changes introduced there.
I have dropped __oom_kill_process part because this one turned out
to be harmless for for the sysrq+f path - I couldn't have found any
interruptible sleep after exit_signals.
I find the resulting code easier to follow (35 (+), 22 (-) sounds like a
reasonable code overhead for that purpose).
--
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 reply other threads:[~2015-06-18 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 9:57 Michal Hocko [this message]
2015-06-18 9:57 ` [PATCH 1/2] oom: Do not panic when OOM killer is sysrq triggered Michal Hocko
2015-06-18 19:21 ` David Rientjes
2015-06-19 7:09 ` Michal Hocko
2015-06-18 9:57 ` [PATCH 2/2] oom: split out forced OOM killer Michal Hocko
2015-06-18 19:27 ` David Rientjes
2015-06-19 7:13 ` Michal Hocko
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=1434621447-21175-1-git-send-email-mhocko@suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox