linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Harry Yoo <harry.yoo@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@gentwo.org>,
	David Rientjes <rientjes@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Hao Li <hao.li@linux.dev>,
	linux-mm@kvack.org, Chris Bainbridge <chris.bainbridge@gmail.com>
Subject: Re: [PATCH] mm/slab: pass __GFP_NOWARN to refill_sheaf() if fallback is available
Date: Mon, 23 Feb 2026 17:48:25 +0100	[thread overview]
Message-ID: <e4f3b873-7825-46e3-831c-d0f5d3761ce4@kernel.org> (raw)
In-Reply-To: <20260223133322.16705-1-harry.yoo@oracle.com>

On 2/23/26 14:33, Harry Yoo wrote:
> When refill_sheaf() is called, failing to refill the sheaf doesn't
> necessarily mean the allocation will fail because a fallback path
> might be available and serve the allocation request.
> 
> Suppress spurious warnings by passing __GFP_NOWARN along with
> __GFP_NOMEMALLOC whenever a fallback path is available.
> 
> When the caller is alloc_full_sheaf() or __pcs_replace_empty_main(),
> the kernel always falls back to the slowpath (__slab_alloc_node()).
> For __prefill_sheaf_pfmemalloc(), the fallback path is available
> only when gfp_pfmemalloc_allowed() returns true.
> 
> Reported-by: Chris Bainbridge <chris.bainbridge@gmail.com>
> Closes: https://lore.kernel.org/linux-mm/aZt2-oS9lkmwT7Ch@debian.local
> Fixes: 1ce20c28eafd ("slab: handle pfmemalloc slabs properly with sheaves")
> Link: https://lore.kernel.org/linux-mm/aZwSreGj9-HHdD-j@hyeyoo
> Signed-off-by: Harry Yoo <harry.yoo@oracle.com>

Thanks, added to slab/for-next-fixes.
Hopefully Chris can confirm it works (without adding the __NOWARN to btrfs code)

> ---
>  mm/slub.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/slub.c b/mm/slub.c
> index afa98065d74f..0c986c240bf6 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -2823,7 +2823,7 @@ static struct slab_sheaf *alloc_full_sheaf(struct kmem_cache *s, gfp_t gfp)
>  	if (!sheaf)
>  		return NULL;
>  
> -	if (refill_sheaf(s, sheaf, gfp | __GFP_NOMEMALLOC)) {
> +	if (refill_sheaf(s, sheaf, gfp | __GFP_NOMEMALLOC | __GFP_NOWARN)) {
>  		free_empty_sheaf(s, sheaf);
>  		return NULL;
>  	}
> @@ -4576,7 +4576,7 @@ __pcs_replace_empty_main(struct kmem_cache *s, struct slub_percpu_sheaves *pcs,
>  		return NULL;
>  
>  	if (empty) {
> -		if (!refill_sheaf(s, empty, gfp | __GFP_NOMEMALLOC)) {
> +		if (!refill_sheaf(s, empty, gfp | __GFP_NOMEMALLOC | __GFP_NOWARN)) {
>  			full = empty;
>  		} else {
>  			/*
> @@ -4891,9 +4891,14 @@ EXPORT_SYMBOL(kmem_cache_alloc_node_noprof);
>  static int __prefill_sheaf_pfmemalloc(struct kmem_cache *s,
>  				      struct slab_sheaf *sheaf, gfp_t gfp)
>  {
> -	int ret = 0;
> +	gfp_t gfp_nomemalloc;
> +	int ret;
> +
> +	gfp_nomemalloc = gfp | __GFP_NOMEMALLOC;
> +	if (gfp_pfmemalloc_allowed(gfp))
> +		gfp_nomemalloc |= __GFP_NOWARN;
>  
> -	ret = refill_sheaf(s, sheaf, gfp | __GFP_NOMEMALLOC);
> +	ret = refill_sheaf(s, sheaf, gfp_nomemalloc);
>  
>  	if (likely(!ret || !gfp_pfmemalloc_allowed(gfp)))
>  		return ret;



      reply	other threads:[~2026-02-23 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 13:33 Harry Yoo
2026-02-23 16:48 ` Vlastimil Babka (SUSE) [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=e4f3b873-7825-46e3-831c-d0f5d3761ce4@kernel.org \
    --to=vbabka@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris.bainbridge@gmail.com \
    --cc=cl@gentwo.org \
    --cc=hao.li@linux.dev \
    --cc=harry.yoo@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=vbabka@suse.cz \
    /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