Re: [PATCH bpf v2] bpf: fix BPF_F_CPU validation for sparse CPU IDs
| Newsgroups | org.kernel.vger.bpf,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178733460914.1412990.11377910972320071983.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to bpf/bpf.git (master) by Andrii Nakryiko <[email protected]>: On Fri, 14 Aug 2026 00:09:00 +0800 you wrote: > BPF_F_CPU stores the target CPU ID in the upper 32 bits of the map > operation flags. bpf_map_check_op_flags() currently compares that ID > with num_possible_cpus(), which is the number of possible CPUs rather > than a bound on CPU IDs. > > On an arm64 QEMU guest with a CPU device-tree hole, the possible CPU > mask was 0,2-3. A userspace program using raw bpf() syscalls creates > a BPF_MAP_TYPE_PERCPU_ARRAY and performs update and lookup operations > for each CPU by setting BPF_F_CPU and the CPU ID in the flags. > > [...] Here is the summary with links: - [bpf,v2] bpf: fix BPF_F_CPU validation for sparse CPU IDs https://git.kernel.org/bpf/bpf/c/ed54bf564ac5 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html