The patch titled
Subject: mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill-v2
has been removed from the -mm tree. Its filename was
mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill-v2.patch
This patch was dropped because it was folded into mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill.patch
------------------------------------------------------
From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
Subject: mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill-v2
Cc: Michal Hocko <mhocko@xxxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/oom_kill.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff -puN mm/oom_kill.c~mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill-v2 mm/oom_kill.c
--- a/mm/oom_kill.c~mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill-v2
+++ a/mm/oom_kill.c
@@ -563,7 +563,11 @@ void oom_kill_process(struct oom_control
/* mm cannot safely be dereferenced after task_unlock(victim) */
mm = victim->mm;
- /* Send SIGKILL before setting TIF_MEMDIE. */
+ /*
+ * We should send SIGKILL before setting TIF_MEMDIE in order to prevent
+ * the OOM victim from depleting the memory reserves from the user
+ * space under its control.
+ */
do_send_sig_info(SIGKILL, SEND_SIG_FORCED, victim, true);
mark_oom_victim(victim);
pr_err("Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB\n",
_
Patches currently in -mm which might be from penguin-kernel@xxxxxxxxxxxxxxxxxxx are
mmoom-reverse-the-order-of-setting-tif_memdie-and-sending-sigkill.patch
mmoom-fix-potentially-killing-unrelated-process.patch
mmoom-suppress-unnecessary-sharing-same-memory-message.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
