[Devel] [PATCH 17/17] oom: do not dump all tasks info on each oom kill

Vladimir Davydov vdavydov at parallels.com
Fri Aug 14 10:03:41 PDT 2015


If there is a fork bomb in a container, it will only spam the dmesg.
Besides, it will take too long to print, probably breaking the berserker
logic. So disable it by default as it used to be in PCS6.

Signed-off-by: Vladimir Davydov <vdavydov at parallels.com>
---
 mm/oom_kill.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 6dec59129bba..8fc8d6b81387 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -42,7 +42,7 @@
 
 int sysctl_panic_on_oom;
 int sysctl_oom_kill_allocating_task;
-int sysctl_oom_dump_tasks = 1;
+int sysctl_oom_dump_tasks;
 int sysctl_oom_timeout = 5 * HZ;
 int sysctl_oom_relaxation = HZ;
 static struct oom_context global_oom_ctx;
-- 
2.1.4




More information about the Devel mailing list