From: Uladzislau Rezki <urezki@gmail.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
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 15:40:10 +0200 [thread overview]
Message-ID: <anCaOuePqh0IUX52@milan> (raw)
In-Reply-To: <pi25qtpcxjhykyc7xwjvvgnlnam2gyp6rxoxsxj5vzfscg5ysp@6wzaipk3t6bm>
On Mon, Aug 03, 2026 at 09:19:52AM +0530, Anshuman Khandual wrote:
> On Sun, Aug 02, 2026 at 12:46:27PM +0200, 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.
>
> Dropping WARN_ON_ONCE() just for -ENOMEM while preserving this
> warning for other returned errors does make sense.
>
> >
> > Reported-by: syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.com
>
> Very small nit.
>
> If there is actual link for the problem report, probably it could
> be added as an Link: or Closes: here.
>
I hope Andrew can help here. If not i will resend!
Thank you!
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-08-03 13:40 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 [this message]
2026-08-03 6:34 ` Baoquan He
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=anCaOuePqh0IUX52@milan \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.