Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

mm/vmalloc: warn on invalid vmalloc gfp flags

Patch series "make vmalloc gfp flags usage more apparent", v4.

We should do a better job at enforcing gfp flags for vmalloc. Right now,
we have a kernel-doc for __vmalloc_node_range(), and hope callers pass in
supported flags. If a caller were to pass in an unsupported flag, we may
BUG, silently clear it, or completely ignore it.

If we are more proactive about enforcing gfp flags, we can making sure
callers know when they may be asking for unsupported behavior.

This patchset lets vmalloc control the incoming gfp flags, and cleans up
some hard to read gfp code.


This patch (of 4):

Vmalloc explicitly supports a list of flags, but we never enforce them.
vmalloc has been trying to handle unsupported flags by clearing and
setting flags wherever necessary. This is messy and makes the code harder
to understand, when we could simply check for a supported input
immediately instead.

Define a helper mask and function telling callers they have passed in
invalid flags, and clear those unsupported vmalloc flags.

Link: https://lkml.kernel.org/r/20251121094405.40628-1-vishal.moola@gmail.com
Link: https://lkml.kernel.org/r/20251121094405.40628-2-vishal.moola@gmail.com
Signed-off-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
Suggested-by: Christoph Hellwig <hch@infradead.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
Acked-by: SeongJae Park <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

authored by

Vishal Moola (Oracle) and committed by
Andrew Morton
07003531 c1bd0999

+26
+26
mm/vmalloc.c
··· 3911 3911 return NULL; 3912 3912 } 3913 3913 3914 + /* 3915 + * See __vmalloc_node_range() for a clear list of supported vmalloc flags. 3916 + * This gfp lists all flags currently passed through vmalloc. Currently, 3917 + * __GFP_ZERO is used by BPF and __GFP_NORETRY is used by percpu. Both drm 3918 + * and BPF also use GFP_USER. Additionally, various users pass 3919 + * GFP_KERNEL_ACCOUNT. Xfs uses __GFP_NOLOCKDEP. 3920 + */ 3921 + #define GFP_VMALLOC_SUPPORTED (GFP_KERNEL | GFP_ATOMIC | GFP_NOWAIT |\ 3922 + __GFP_NOFAIL | __GFP_ZERO | __GFP_NORETRY |\ 3923 + GFP_NOFS | GFP_NOIO | GFP_KERNEL_ACCOUNT |\ 3924 + GFP_USER | __GFP_NOLOCKDEP) 3925 + 3926 + static gfp_t vmalloc_fix_flags(gfp_t flags) 3927 + { 3928 + gfp_t invalid_mask = flags & ~GFP_VMALLOC_SUPPORTED; 3929 + 3930 + flags &= GFP_VMALLOC_SUPPORTED; 3931 + WARN_ONCE(1, "Unexpected gfp: %#x (%pGg). Fixing up to gfp: %#x (%pGg). Fix your code!\n", 3932 + invalid_mask, &invalid_mask, flags, &flags); 3933 + return flags; 3934 + } 3935 + 3914 3936 /** 3915 3937 * __vmalloc_node_range - allocate virtually contiguous memory 3916 3938 * @size: allocation size ··· 4114 4092 4115 4093 void *__vmalloc_noprof(unsigned long size, gfp_t gfp_mask) 4116 4094 { 4095 + if (unlikely(gfp_mask & ~GFP_VMALLOC_SUPPORTED)) 4096 + gfp_mask = vmalloc_fix_flags(gfp_mask); 4117 4097 return __vmalloc_node_noprof(size, 1, gfp_mask, NUMA_NO_NODE, 4118 4098 __builtin_return_address(0)); 4119 4099 } ··· 4155 4131 */ 4156 4132 void *vmalloc_huge_node_noprof(unsigned long size, gfp_t gfp_mask, int node) 4157 4133 { 4134 + if (unlikely(gfp_mask & ~GFP_VMALLOC_SUPPORTED)) 4135 + gfp_mask = vmalloc_fix_flags(gfp_mask); 4158 4136 return __vmalloc_node_range_noprof(size, 1, VMALLOC_START, VMALLOC_END, 4159 4137 gfp_mask, PAGE_KERNEL, VM_ALLOW_HUGE_VMAP, 4160 4138 node, __builtin_return_address(0));