From: Vlastimil Babka <vbabka@suse.cz>
To: Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH] kfence: skip __GFP_THISNODE allocations on NUMA systems
Date: Fri, 24 Jan 2025 15:05:10 +0100 [thread overview]
Message-ID: <d4a7b91e-5048-496e-95e5-c83cd8252d8f@suse.cz> (raw)
In-Reply-To: <20250124120145.410066-1-elver@google.com>
On 1/24/25 13:01, Marco Elver wrote:
> On NUMA systems, __GFP_THISNODE indicates that an allocation _must_ be
> on a particular node, and failure to allocate on the desired node will
> result in a failed allocation.
>
> Skip __GFP_THISNODE allocations if we are running on a NUMA system,
> since KFENCE can't guarantee which node its pool pages are allocated on.
>
> Reported-by: Vlastimil Babka <vbabka@suse.cz>
> Cc: Christoph Lameter <cl@linux.com>
> Fixes: 236e9f153852 ("kfence: skip all GFP_ZONEMASK allocations")
> Signed-off-by: Marco Elver <elver@google.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Thanks.
> ---
> mm/kfence/core.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 67fc321db79b..102048821c22 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -21,6 +21,7 @@
> #include <linux/log2.h>
> #include <linux/memblock.h>
> #include <linux/moduleparam.h>
> +#include <linux/nodemask.h>
> #include <linux/notifier.h>
> #include <linux/panic_notifier.h>
> #include <linux/random.h>
> @@ -1084,6 +1085,7 @@ void *__kfence_alloc(struct kmem_cache *s, size_t size, gfp_t flags)
> * properties (e.g. reside in DMAable memory).
> */
> if ((flags & GFP_ZONEMASK) ||
> + ((flags & __GFP_THISNODE) && num_online_nodes() > 1) ||
> (s->flags & (SLAB_CACHE_DMA | SLAB_CACHE_DMA32))) {
> atomic_long_inc(&counters[KFENCE_COUNTER_SKIP_INCOMPAT]);
> return NULL;
prev parent reply other threads:[~2025-01-24 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 12:01 Marco Elver
2025-01-24 14:05 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4a7b91e-5048-496e-95e5-c83cd8252d8f@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox