From: patchwork-bot+netdevbpf@kernel.org
To: Guannan Wang <wgnbuaa@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net,
gregkh@linuxfoundation.org, ast@kernel.org, andrii@kernel.org,
xlabai@tencent.com
Subject: Re: [PATCH bpf] bpf: Use array_map_meta_equal for percpu array inner map replacement
Date: Thu, 14 May 2026 15:30:05 +0000 [thread overview]
Message-ID: <177877260580.4176003.17875178222309758286.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514074454.77491-1-wgnbuaa@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 14 May 2026 15:44:54 +0800 you wrote:
> percpu_array_map_ops.map_meta_equal points to the generic
> bpf_map_meta_equal(), which does not compare max_entries. When a
> percpu array serves as an inner map, replacing it with one that has
> fewer max_entries bypasses the check. Since percpu_array_map_gen_lookup()
> inlines the original template's index_mask as a JIT immediate, a lookup
> on the replacement map can access pptrs[] out of bounds.
>
> [...]
Here is the summary with links:
- [bpf] bpf: Use array_map_meta_equal for percpu array inner map replacement
https://git.kernel.org/bpf/bpf/c/593980175389
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-14 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 7:44 [PATCH bpf] bpf: Use array_map_meta_equal for percpu array inner map replacement Guannan Wang
2026-05-14 12:39 ` Mykyta Yatsenko
2026-05-14 15:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177877260580.4176003.17875178222309758286.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=wgnbuaa@gmail.com \
--cc=xlabai@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.