linux-kernel - Re: [PATCH v3] mm, oom: OOM sysrq should always kill a process

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] [day] [month] [year] [list]

Message-ID: <ae727710-7298-ca63-fcb0-9f8b84d94bee@google.com>
Date:   Thu, 6 Jan 2022 12:34:19 -0800 (PST)
From:   David Rientjes <rientjes@...gle.com>
To:     Jann Horn <jannh@...gle.com>
cc:     Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH v3] mm, oom: OOM sysrq should always kill a process

On Thu, 6 Jan 2022, Jann Horn wrote:

> The OOM kill sysrq (alt+sysrq+F) should allow the user to kill the
> process with the highest OOM badness with a single execution.
> 
> However, at the moment, the OOM kill can bail out if an OOM notifier
> (e.g. the i915 one) says that it reclaimed a tiny amount of memory
> from somewhere. That's probably not what the user wants, so skip the
> bailout if the OOM was triggered via sysrq.
> 
> Acked-by: Michal Hocko <mhocko@...e.com>
> Signed-off-by: Jann Horn <jannh@...gle.com>

Acked-by: David Rientjes <rientjes@...gle.com>