diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-05-02 13:56:48 +0200 | 
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-05-02 13:56:48 +0200 | 
| commit | 0e509f537f8ddd89f237e62f77818dbdbc8be395 (patch) | |
| tree | 4e747a1cad81d0c085d435923366bcce30484bc8 /mm/util.c | |
| parent | f8ae07f4b8bfde0f33761e1a1aaee45a4e85e9d6 (diff) | |
| parent | 672c0c5173427e6b3e2a9bbb7be51ceeec78093a (diff) | |
Merge 5.18-rc5 into driver-core-next
We need the kernfs/driver core fixes in here as well.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/util.c')
| -rw-r--r-- | mm/util.c | 11 | 
1 files changed, 9 insertions, 2 deletions
diff --git a/mm/util.c b/mm/util.c index 54e5e761a9a9..3492a9e81aa3 100644 --- a/mm/util.c +++ b/mm/util.c @@ -592,8 +592,15 @@ void *kvmalloc_node(size_t size, gfp_t flags, int node)  		return NULL;  	} -	return __vmalloc_node(size, 1, flags, node, -			__builtin_return_address(0)); +	/* +	 * kvmalloc() can always use VM_ALLOW_HUGE_VMAP, +	 * since the callers already cannot assume anything +	 * about the resulting pointer, and cannot play +	 * protection games. +	 */ +	return __vmalloc_node_range(size, 1, VMALLOC_START, VMALLOC_END, +			flags, PAGE_KERNEL, VM_ALLOW_HUGE_VMAP, +			node, __builtin_return_address(0));  }  EXPORT_SYMBOL(kvmalloc_node);  | 
