From: Toke Høiland-Jørgensen Date: Thu, 16 Apr 2020 08:31:20 +0000 (+0200) Subject: cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled X-Git-Tag: v5.15~3983^2^2~16 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=bc23d0e3f717ced21fbfacab3ab887d55e5ba367;p=platform%2Fkernel%2Flinux-starfive.git cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled When the kernel is built with CONFIG_DEBUG_PER_CPU_MAPS, the cpumap code can trigger a spurious warning if CONFIG_CPUMASK_OFFSTACK is also set. This happens because in this configuration, NR_CPUS can be larger than nr_cpumask_bits, so the initial check in cpu_map_alloc() is not sufficient to guard against hitting the warning in cpumask_check(). Fix this by explicitly checking the supplied key against the nr_cpumask_bits variable before calling cpu_possible(). Fixes: 6710e1126934 ("bpf: introduce new bpf cpu map type BPF_MAP_TYPE_CPUMAP") Reported-by: Xiumei Mu Signed-off-by: Toke Høiland-Jørgensen Signed-off-by: Alexei Starovoitov Tested-by: Xiumei Mu Acked-by: Jesper Dangaard Brouer Acked-by: Song Liu Link: https://lore.kernel.org/bpf/20200416083120.453718-1-toke@redhat.com --- diff --git a/kernel/bpf/cpumap.c b/kernel/bpf/cpumap.c index 70f71b1..3fe0b00 100644 --- a/kernel/bpf/cpumap.c +++ b/kernel/bpf/cpumap.c @@ -469,7 +469,7 @@ static int cpu_map_update_elem(struct bpf_map *map, void *key, void *value, return -EOVERFLOW; /* Make sure CPU is a valid possible cpu */ - if (!cpu_possible(key_cpu)) + if (key_cpu >= nr_cpumask_bits || !cpu_possible(key_cpu)) return -ENODEV; if (qsize == 0) {