bpf: Make __GFP_NOWARN consistent in bpf map creation
authorYafang Shao <laoar.shao@gmail.com>
Wed, 10 Aug 2022 15:18:28 +0000 (15:18 +0000)
committerAlexei Starovoitov <ast@kernel.org>
Wed, 10 Aug 2022 18:49:25 +0000 (11:49 -0700)
commit992c9e13f5939437037627c67bcb51e674b64265
treedbde02aae2f7eb6f549abcc2a6e7b4087cf93fe5
parent8f58ee54c2eae790f50c51dfa64a153601451f08
bpf: Make __GFP_NOWARN consistent in bpf map creation

Some of the bpf maps are created with __GFP_NOWARN, i.e. arraymap,
bloom_filter, bpf_local_storage, bpf_struct_ops, lpm_trie,
queue_stack_maps, reuseport_array, stackmap and xskmap, while others are
created without __GFP_NOWARN, i.e. cpumap, devmap, hashtab,
local_storage, offload, ringbuf and sock_map. But there are not key
differences between the creation of these maps. So let make this
allocation flag consistent in all bpf maps creation. Then we can use a
generic helper to alloc all bpf maps.

Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Link: https://lore.kernel.org/r/20220810151840.16394-4-laoar.shao@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
kernel/bpf/cpumap.c
kernel/bpf/devmap.c
kernel/bpf/hashtab.c
kernel/bpf/local_storage.c
kernel/bpf/offload.c
kernel/bpf/ringbuf.c
net/core/sock_map.c