Re: WARNING in try_charge

From: Tetsuo Handa
Date: Mon Aug 06 2018 - 16:26:35 EST

On 2018/08/07 2:56, Michal Hocko wrote:
> So the oom victim indeed passed the above force path after the oom
> invocation. But later on hit the page fault path and that behaved
> differently and for some reason the force path hasn't triggered. I am
> wondering how could we hit the page fault path in the first place. The
> task is already killed! So what the hell is going on here.
> I must be missing something obvious here.

I already said this is "mm, oom: task_will_free_mem(current) should ignore MMF_OOM_SKIP for once."
problem which you are refusing at .
And you again ignored my mail. Very sad...