The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Baoquan He <baoquan.he@linux.dev>
To: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Baoquan He <bhe@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.com
Subject: Re: [PATCH] mm/vmalloc: Do not warn on -ENOMEM from va_alloc()
Date: Mon, 3 Aug 2026 14:34:12 +0800	[thread overview]
Message-ID: <anA2ZInokBWZI5yK@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260802104627.63892-1-urezki@gmail.com>

On 08/02/26 at 12:46pm, Uladzislau Rezki (Sony) wrote:
> Since vmalloc() accepts non-blocking GFP flags, allocation
> requests may fail when callers pass restrictive GFP masks.
> 
> va_clip() may return -ENOMEM when its GFP_NOWAIT fallback
> allocation fails during NE_FIT_TYPE splitting. This is an
> expected failure, so va_alloc() should return the error
> without triggering a kernel splat.
> 
> Reported-by: syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.com
> Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
> ---
>  mm/vmalloc.c | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 1afca3568b9b..7a0cbba3d29d 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -1817,8 +1817,10 @@ va_alloc(struct vmap_area *va,
>  
>  	/* Update the free vmap_area. */
>  	ret = va_clip(root, head, va, nva_start_addr, size);
> -	if (WARN_ON_ONCE(ret))
> +	if (ret) {
> +		WARN_ON_ONCE(ret != -ENOMEM);
>  		return ret;
> +	}
>  
>  	return nva_start_addr;
>  }
> @@ -1891,12 +1893,9 @@ preload_this_cpu_lock(spinlock_t *lock, gfp_t gfp_mask, int node)
>  
>  	/*
>  	 * Preload this CPU with one extra vmap_area object. It is used
> -	 * when fit type of free area is NE_FIT_TYPE. It guarantees that
> -	 * a CPU that does an allocation is preloaded.
> -	 *
> -	 * We do it in non-atomic context, thus it allows us to use more
> -	 * permissive allocation masks to be more stable under low memory
> -	 * condition and high memory pressure.
> +	 * when fit type of free area is NE_FIT_TYPE. It is best effort
> +	 * pre-loading. If it fails va_clip() may return -ENOMEM from its
> +	 * GFP_NOWAIT fallback.
>  	 */
>  	if (!this_cpu_read(ne_fit_preload_node))
>  		va = kmem_cache_alloc_node(vmap_area_cachep, gfp_mask, node);

LGTM,

Reviewed-by: Baoquan He <baoquan.he@linux.dev>


      parent reply	other threads:[~2026-08-03  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 10:46 [PATCH] mm/vmalloc: Do not warn on -ENOMEM from va_alloc() Uladzislau Rezki (Sony)
2026-08-03  3:49 ` Anshuman Khandual
2026-08-03 13:40   ` Uladzislau Rezki
2026-08-03  6:34 ` Baoquan He [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=anA2ZInokBWZI5yK@MiWiFi-R3L-srv \
    --to=baoquan.he@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.com \
    --cc=urezki@gmail.com \
    /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