Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case

[Aaron Tomlin]

On Thu 2021-06-10 23:06 +0900, Tetsuo Handa wrote:
> Yes, marking ineligible (i.e. oom_badness() returning LONG_MIN) tasks
> would be useful.

Sure. I'll send a patch to append this information; and the reason why
i.e. "yes: oom skipped" or "yes: oom score" or "yes: vfork" to dump_task()
with the use of some helper function e.g. is_task_eligible_oom().

> By the way, was the task namely "node" (i.e. PID 1703345) multithreaded
> program?

Unfortunately, I cannot confirm since the scenario/or situation is no
longer present in the vmcore; albeit, I believe so.

> Your kernel might want commit 7775face207922ea ("memcg: killed threads
> should not invoke memcg OOM killer").

Tetsuo-san,

Yes, this does appear to be a match.
Thanks for this.


Kind regards,

-- 
Aaron Tomlin