[PATCH 04/10] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj

From: Michal Hocko oom_score_adj is shared for the thread groups (via struct signal) but this is not sufficient to cover processes sharing mm (CLONE_VM without CLONE_SIGHAND) and so we can easily end up in a situation when some processes update their oom_score_adj and confuse the oom killer. In t

Re: [PATCH 04/10] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj

On 06/09, Michal Hocko wrote: > > + if (!p->vfork_done && process_shares_mm(p, mm)) { > + pr_info("updating oom_score_adj for %d (%s) > from %d to %d because it shares mm with %d (%s). Report if this is > unexpected.\n", > +

[PATCH 04/10] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj

From: Michal Hocko oom_score_adj is shared for the thread groups (via struct signal) but this is not sufficient to cover processes sharing mm (CLONE_VM without CLONE_SIGHAND) and so we can easily end up in a situation when some processes update their oom_score_adj and confuse the oom killer. In t

[PATCH 04/10] mm, oom_adj: make sure processes sharing mm have same view of oom_score_adj

From: Michal Hocko oom_score_adj is shared for the thread groups (via struct signal) but this is not sufficient to cover processes sharing mm (CLONE_VM without CLONE_THREAD resp. CLONE_SIGHAND) and so we can easily end up in a situation when some processes update their oom_score_adj and confuse t