> The oom killer tasklist dump, enabled with the oom_dump_tasks sysctl, is > very helpful information in diagnosing why a user's task has been killed. > It emits useful information such as each eligible thread's memory usage > that can determine why the system is oom, so it should be enabled by > default. > > Acked-by: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> > Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> > --- > Documentation/sysctl/vm.txt | 2 +- > mm/oom_kill.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/sysctl/vm.txt b/Documentation/sysctl/vm.txt > --- a/Documentation/sysctl/vm.txt > +++ b/Documentation/sysctl/vm.txt > @@ -511,7 +511,7 @@ information may not be desired. > If this is set to non-zero, this information is shown whenever the > OOM killer actually kills a memory-hogging task. > > -The default value is 0. > +The default value is 1 (enabled). > > ============================================================== > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index ef048c1..833de48 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -32,7 +32,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); > /* #define DEBUG */ > pulled. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>