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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210608093949.szz3e6ucpf7mztxr@ava.usersys.com>
Date:   Tue, 8 Jun 2021 10:39:49 +0100
From:   Aaron Tomlin <atomlin@...hat.com>
To:     Michal Hocko <mhocko@...e.com>
Cc:     Waiman Long <llong@...hat.com>, Shakeel Butt <shakeelb@...gle.com>,
        Linux MM <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for
 non-global case

On Tue 2021-06-08 08:22 +0200, Michal Hocko wrote:
> You are saying that there are other OOM kills going on.

Yes.

> Are they all for the same memcg?

No.

> Is it possible the only eligible task has been killed and oom reaped
> already?

Unfortunately, as mentioned by Waiman, no other task is suitable for
"selection" due to the OOM score (i.e. OOM_SCORE_ADJ_MIN;) that said, I
need access to the vmcore to check i.e. mm.flags - I'll get back to you as
soon as I can.


Kind regards,

-- 
Aaron Tomlin