Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Tetsuo Handa
On 2018/09/08 22:57, Johannes Weiner wrote: > On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote: >> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and >> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when >> no eligible victim left"), all >> >>

Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Tetsuo Handa
On 2018/09/08 22:57, Johannes Weiner wrote: > On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote: >> Due to commit d75da004c708c9fc ("oom: improve oom disable handling") and >> commit 3100dab2aa09dc6e ("mm: memcontrol: print proper OOM header when >> no eligible victim left"), all >> >>

Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Johannes Weiner
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote: > On 2018/08/22 1:04, Johannes Weiner wrote: > > When the memcg OOM killer runs out of killable tasks, it currently > > prints a WARN with no further OOM context. This has caused some user > > confusion. > > > > Warnings indicate a

Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Johannes Weiner
On Sat, Sep 08, 2018 at 10:36:06PM +0900, Tetsuo Handa wrote: > On 2018/08/22 1:04, Johannes Weiner wrote: > > When the memcg OOM killer runs out of killable tasks, it currently > > prints a WARN with no further OOM context. This has caused some user > > confusion. > > > > Warnings indicate a

Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Tetsuo Handa
On 2018/08/22 1:04, Johannes Weiner wrote: > When the memcg OOM killer runs out of killable tasks, it currently > prints a WARN with no further OOM context. This has caused some user > confusion. > > Warnings indicate a kernel problem. In a reported case, however, the > situation was triggered by

Re: [PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-09-08 Thread Tetsuo Handa
On 2018/08/22 1:04, Johannes Weiner wrote: > When the memcg OOM killer runs out of killable tasks, it currently > prints a WARN with no further OOM context. This has caused some user > confusion. > > Warnings indicate a kernel problem. In a reported case, however, the > situation was triggered by

[PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-08-21 Thread Johannes Weiner
When the memcg OOM killer runs out of killable tasks, it currently prints a WARN with no further OOM context. This has caused some user confusion. Warnings indicate a kernel problem. In a reported case, however, the situation was triggered by a non-sensical memcg configuration (hard limit set to

[PATCH] mm: memcontrol: print proper OOM header when no eligible victim left

2018-08-21 Thread Johannes Weiner
When the memcg OOM killer runs out of killable tasks, it currently prints a WARN with no further OOM context. This has caused some user confusion. Warnings indicate a kernel problem. In a reported case, however, the situation was triggered by a non-sensical memcg configuration (hard limit set to