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 <khore...@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 5413a44..e5d0b86 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; static DEFINE_SPINLOCK(zone_scan_lock); #ifdef CONFIG_NUMA -- 1.8.3.1 _______________________________________________ Devel mailing list Devel@openvz.org https://lists.openvz.org/mailman/listinfo/devel
