From: Andrew Morton <akpm@linux-foundation.org>
To: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2 0/4] make vmalloc gfp flags usage more apparent
Date: Wed, 12 Nov 2025 14:22:13 -0800 [thread overview]
Message-ID: <20251112142213.bc01a3abe37de98f9d40e392@linux-foundation.org> (raw)
In-Reply-To: <20251112185834.32487-1-vishal.moola@gmail.com>
On Wed, 12 Nov 2025 10:58:29 -0800 "Vishal Moola (Oracle)" <vishal.moola@gmail.com> wrote:
> v2:
> - Add __GFP_HARDWALL[3] for bpf and drm users.
> - cc BPF mailing list
v1->v2 diff:
--- a/mm/vmalloc.c~b
+++ a/mm/vmalloc.c
@@ -3922,10 +3922,12 @@ fail:
/*
* See __vmalloc_node_range() for a clear list of supported vmalloc flags.
* This gfp lists all flags currently passed through vmalloc. Currently,
- * __GFP_ZERO is used by BFP and __GFP_NORETRY is used by percpu.
+ * __GFP_ZERO is used by BPF and __GFP_NORETRY is used by percpu. Both drm
+ * and BPF also use GFP_USER, which is GFP_KERNEL | __GFP_HARDWALL.
*/
#define GFP_VMALLOC_SUPPORTED (GFP_KERNEL | GFP_ATOMIC | GFP_NOWAIT |\
- __GFP_NOFAIL | __GFP_ZERO | __GFP_NORETRY)
+ __GFP_NOFAIL | __GFP_ZERO | __GFP_NORETRY |\
+ __GFP_HARDWALL)
static gfp_t vmalloc_fix_flags(gfp_t flags)
{
_
next prev parent reply other threads:[~2025-11-12 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 18:58 Vishal Moola (Oracle)
2025-11-12 18:58 ` [PATCH v2 1/4] mm/vmalloc: warn on invalid vmalloc gfp flags Vishal Moola (Oracle)
2025-11-12 18:58 ` [PATCH v2 2/4] mm/vmalloc: Add a helper to optimize vmalloc allocation gfps Vishal Moola (Oracle)
2025-11-12 18:58 ` [PATCH v2 3/4] mm/vmalloc: cleanup large_gfp in vm_area_alloc_pages() Vishal Moola (Oracle)
2025-11-12 18:58 ` [PATCH v2 4/4] mm/vmalloc: cleanup gfp flag use in new_vmap_block() Vishal Moola (Oracle)
2025-11-12 22:22 ` Andrew Morton [this message]
2025-11-13 3:48 ` [PATCH v2 0/4] make vmalloc gfp flags usage more apparent Baolin Wang
2025-11-13 16:01 ` Vishal Moola (Oracle)
2025-11-13 7:41 ` [syzbot ci] " syzbot ci
2025-11-13 13:33 ` Uladzislau Rezki
2025-11-13 16:48 ` Vishal Moola (Oracle)
2025-11-13 16:54 ` Uladzislau Rezki
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=20251112142213.bc01a3abe37de98f9d40e392@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.com \
--cc=vishal.moola@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