linux-kernel - Re: [PATCH] mm, slub: print CPU id on slab OOM

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: <4e06d3ee-de78-9a71-ccec-6c0a5aa0c7f6@google.com>
Date: Sat, 10 Aug 2024 16:52:57 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Axel Rasmussen <axelrasmussen@...gle.com>
cc: Andrew Morton <akpm@...ux-foundation.org>, 
    Christoph Lameter <cl@...ux.com>, Hyeonggon Yoo <42.hyeyoo@...il.com>, 
    Joonsoo Kim <iamjoonsoo.kim@....com>, Pekka Enberg <penberg@...nel.org>, 
    Roman Gushchin <roman.gushchin@...ux.dev>, 
    Vlastimil Babka <vbabka@...e.cz>, linux-kernel@...r.kernel.org, 
    linux-mm@...ck.org
Subject: Re: [PATCH] mm, slub: print CPU id on slab OOM

On Tue, 6 Aug 2024, Axel Rasmussen wrote:

> Depending on how remote_node_defrag_ratio is configured, allocations can
> end up in this path as a result of the local node being OOM, despite the
> allocation overall being unconstrained (node == -1).
> 
> When we print a warning, printing the current CPU makes that situation
> more clear (i.e., you can immediately see which node's OOM status
> matters for the allocation at hand).
> 
> Signed-off-by: Axel Rasmussen <axelrasmussen@...gle.com>

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