From: Andrea Arcangeli <andrea@cpushare.com>
To: linux-mm@kvack.org
Subject: [PATCH 03 of 13] prevent oom deadlocks during read/write operations
Date: Tue, 08 Jan 2008 08:50:34 +0100 [thread overview]
Message-ID: <4091a7ef36c80c3d2fa0.1199778634@v2.random> (raw)
In-Reply-To: <patchbomb.1199778631@v2.random>
# HG changeset patch
# User Andrea Arcangeli <andrea@suse.de>
# Date 1199469588 -3600
# Node ID 4091a7ef36c80c3d2fa0d60a7b8bd885da68154d
# Parent ddd02ad798f6902fc561843c60f1189a44fdb439
prevent oom deadlocks during read/write operations
We need to react to SIGKILL during read/write with huge buffers or it
becomes too easy to prevent a SIGKILLED task to run do_exit promptly
after it has been selected for oom-killage.
Signed-off-by: Andrea Arcangeli <andrea@suse.de>
diff --git a/mm/filemap.c b/mm/filemap.c
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -927,6 +927,16 @@ page_ok:
isize = i_size_read(inode);
end_index = (isize - 1) >> PAGE_CACHE_SHIFT;
if (unlikely(!isize || index > end_index)) {
+ page_cache_release(page);
+ goto out;
+ }
+
+ if (unlikely(sigismember(¤t->pending.signal, SIGKILL))) {
+ /*
+ * Must not hang almost forever in D state in
+ * presence of sigkill and lots of ram/swap
+ * (think during OOM).
+ */
page_cache_release(page);
goto out;
}
@@ -2063,6 +2073,16 @@ static ssize_t generic_perform_write_2co
break;
}
+ if (unlikely(sigismember(¤t->pending.signal, SIGKILL))) {
+ /*
+ * Must not hang almost forever in D state in
+ * presence of sigkill and lots of ram/swap
+ * (think during OOM).
+ */
+ status = -ENOMEM;
+ break;
+ }
+
page = __grab_cache_page(mapping, index);
if (!page) {
status = -ENOMEM;
@@ -2230,6 +2250,16 @@ again:
*/
if (unlikely(iov_iter_fault_in_readable(i, bytes))) {
status = -EFAULT;
+ break;
+ }
+
+ if (unlikely(sigismember(¤t->pending.signal, SIGKILL))) {
+ status = -ENOMEM;
+ /*
+ * Must not hang almost forever in D state in
+ * presence of sigkill and lots of ram/swap
+ * (think during OOM).
+ */
break;
}
--
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:[~2008-01-08 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 7:50 [PATCH 00 of 13] oom deadlock fixes # try 2 Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 01 of 13] limit shrink zone scanning Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 02 of 13] avoid oom deadlock in nfs_create_request Andrea Arcangeli
2008-01-08 7:50 ` Andrea Arcangeli [this message]
2008-01-08 7:50 ` [PATCH 04 of 13] avoid selecting already killed tasks Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 05 of 13] reduce the probability of an OOM livelock Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 06 of 13] balance_pgdat doesn't return the number of pages freed Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 07 of 13] don't depend on PF_EXITING tasks to go away Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 08 of 13] stop useless vm trashing while we wait the TIF_MEMDIE task to exit Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 09 of 13] oom select should only take rss into account Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 10 of 13] limit reclaim if enough pages have been freed Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 11 of 13] not-wait-memdie Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 12 of 13] gfp-repeat stop with TIF_MEMDIE Andrea Arcangeli
2008-01-08 7:50 ` [PATCH 13 of 13] congestion wait Andrea Arcangeli
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=4091a7ef36c80c3d2fa0.1199778634@v2.random \
--to=andrea@cpushare.com \
--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