[Devel] [PATCH RHEL7 COMMIT] oom: Revert "oom: do not dump all tasks info on each oom kill"

[Konstantin Khorenko]

The commit is pushed to "branch-rh7-3.10.0-229.7.2.vz7.8.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-229.7.2.vz7.8.8
------>
commit ff7cacf5ce32fb0047e36875ba329b9f338a38f9
Author: Konstantin Khorenko <khorenko at virtuozzo.com>
Date:   Tue Oct 20 15:54:35 2015 +0400

    oom: Revert "oom: do not dump all tasks info on each oom kill"
    
    This reverts commit 4c6ca842a16f63816407247a696360b77348a566.
    
    The information about the resource usage of tasks when OOM is
    triggered often is the only source of info which can be investigated
    to understand if there is a problem on the node =>
    enable it by default back.
    
    OOM reports are ratelimited to 1 per 5 secs by default
    so even fork bomb's ability to spam messages is limited.
    
    Signed-off-by: Konstantin Khorenko <khorenko at virtuozzo.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 6d16154..71d88ad 100644
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -41,7 +41,7 @@
 
 int sysctl_panic_on_oom;
 int sysctl_oom_kill_allocating_task;
-int sysctl_oom_dump_tasks;
+int sysctl_oom_dump_tasks = 1;
 int sysctl_oom_relaxation = HZ;
 
 static DEFINE_SPINLOCK(oom_context_lock);