From: Leon Hwang <leon.hwang@linux.dev>
To: Emil Tsalapatis <emil@etsalapatis.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Quentin Monnet <qmo@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v10 2/9] bpf: Introduce global percpu data
Date: Mon, 20 Jul 2026 12:59:02 +0800 [thread overview]
Message-ID: <9615cf9b-4a77-4d7a-aec4-8990ea6ff638@linux.dev> (raw)
In-Reply-To: <DK0MRMWIAE1T.20UJQKK2YN3VY@etsalapatis.com>
On 17/7/26 14:25, Emil Tsalapatis wrote:
> On Wed Jul 15, 2026 at 11:32 AM EDT, Leon Hwang wrote:
[...]
>>
>> +static int percpu_array_map_direct_value_addr(const struct bpf_map *map, u64 *imm, u32 off)
>> +{
>> + struct bpf_array *array = container_of(map, struct bpf_array, map);
>> +
>> + if (map->max_entries != 1)
>> + return -EOPNOTSUPP;
>> + if (off >= map->value_size)
>> + return -EINVAL;
>> + if (!bpf_jit_supports_percpu_insn())
>> + return -EOPNOTSUPP;
>
> Nit: This should be first, if the JIT doesn't support the instruction
> all else is moot. Same below.
Ack.
>
>> +
>> + *imm = (u64)(__force unsigned long) array->pptrs[0];
>> + return 0;
>> +}
>> +
>> +static int percpu_array_map_direct_value_meta(const struct bpf_map *map, u64 imm, u32 *off)
>> +{
>> + struct bpf_array *array = container_of(map, struct bpf_array, map);
>> + u64 base = (u64)(__force unsigned long) array->pptrs[0];
>> +
>> + if (map->max_entries != 1)
>> + return -EOPNOTSUPP;
>> + if (imm < base || imm >= base + array->elem_size)
>> + return -ENOENT;
>> + if (!bpf_jit_supports_percpu_insn())
>> + return -EOPNOTSUPP;
>> +
>> + *off = imm - base;
>> + return 0;
>> +}
>> +
[...]
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index e1244a721194..ae442ea217c4 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -5615,6 +5615,8 @@ int bpf_map_direct_read(struct bpf_map *map, int off, int size, u64 *val,
>> u64 addr;
>> int err;
>>
>> + if (map->map_type == BPF_MAP_TYPE_INSN_ARRAY || map->map_type == BPF_MAP_TYPE_PERCPU_ARRAY)
>> + return -EINVAL;
>> err = map->ops->map_direct_value_addr(map, &addr, off);
>> if (err)
>> return err;
>> @@ -6174,6 +6176,7 @@ static int check_mem_access(struct bpf_verifier_env *env, int insn_idx, struct b
>> if (tnum_is_const(reg->var_off) &&
>> bpf_map_is_rdonly(map) &&
>> map->ops->map_direct_value_addr &&
>> + map->map_type != BPF_MAP_TYPE_PERCPU_ARRAY &&
>> map->map_type != BPF_MAP_TYPE_INSN_ARRAY) {
>
> An issue I have with the patch is that it takes the special-casing we
> already have for INSN_ARRAY and makes it worse. The instruction arrays
> implement direct_value_addr, but it's not actually valid to call
> direct_value_addr from a bunch of places where it's called, so we have
> to special case check the map type to prevent it. Case in point the
> special casing in check_arg_const_str in the thunk below.
>
> Imo we should consider making a different map method different from
> direct_value_addr that INSN_ARRAY and PERCPU_ARRAY implement. That way
> we remove most of the map type checks in those paths. I'm not exactly
> sure how that would look like, but I could take a look at it tomorrow.
Seems reasonable to me. I don't have good candidates for the new map
method name.
Instead of making a new map method, how about factoring out a helper for
the 'if (t == BPF_READ && value_regno >= 0) {}' block? It will simplify
these map_type checks in the helper.
>
>> int map_off = off + reg->var_off.value;
>> u64 val = 0;
>> @@ -8176,6 +8179,12 @@ static int check_arg_const_str(struct bpf_verifier_env *env,
>> return -EACCES;
>> }
>>
>> + if (map->map_type == BPF_MAP_TYPE_PERCPU_ARRAY) {
>> + verbose(env, "%s points to percpu_array map which cannot be used as const string\n",
>> + reg_arg_name(env, argno));
>> + return -EACCES;
>> + }
>> +
>> if (!bpf_map_is_rdonly(map)) {
>> verbose(env, "%s does not point to a readonly map'\n", reg_arg_name(env, argno));
>> return -EACCES;
>> @@ -18279,6 +18288,12 @@ static int check_and_resolve_insns(struct bpf_verifier_env *env)
>> return -EINVAL;
>> }
>>
>> + if (map->map_type == BPF_MAP_TYPE_PERCPU_ARRAY &&
>> + !env->prog->jit_requested) {
>> + verbose(env, "JIT is required to use global percpu data\n");
>> + return -EOPNOTSUPP;
>> + }
>> +
>
> Another place where we add map-specific checks where there are none.
I think this check is unnecessary, because 'prog->jit_required = true'
has been set for global percpu data.
Will drop this if.
Thanks,
Leon
>
>> err = map->ops->map_direct_value_addr(map, &addr, off);
>> if (err) {
>> verbose(env, "invalid access to map value pointer, value_size=%u off=%u\n",
>
next prev parent reply other threads:[~2026-07-20 4:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:32 [PATCH bpf-next v10 0/9] bpf: Introduce global percpu data Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 1/9] bpf: Drop duplicate blank lines in verifier Leon Hwang
2026-07-17 5:08 ` Emil Tsalapatis
2026-07-17 5:28 ` Leon Hwang
2026-07-21 13:48 ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 2/9] bpf: Introduce global percpu data Leon Hwang
2026-07-17 6:25 ` Emil Tsalapatis
2026-07-20 4:59 ` Leon Hwang [this message]
2026-07-20 22:55 ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 3/9] libbpf: Probe percpu data feature Leon Hwang
2026-07-17 21:52 ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 4/9] libbpf: Add support for global percpu data Leon Hwang
2026-07-17 21:39 ` Emil Tsalapatis
2026-07-20 4:59 ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 5/9] bpftool: Generate skeleton " Leon Hwang
2026-07-17 21:52 ` Emil Tsalapatis
2026-07-20 5:00 ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 6/9] selftests/bpf: Add tests to verify " Leon Hwang
2026-07-15 16:11 ` bot+bpf-ci
2026-07-16 5:30 ` Leon Hwang
2026-07-17 22:47 ` Emil Tsalapatis
2026-07-20 5:02 ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 7/9] selftests/bpf: Test direct reading/writing read-only percpu_array map Leon Hwang
2026-07-17 22:49 ` Emil Tsalapatis
2026-07-20 5:03 ` Leon Hwang
2026-07-15 15:32 ` [PATCH bpf-next v10 8/9] selftests/bpf: Test verifier log for global percpu data Leon Hwang
2026-07-17 22:50 ` Emil Tsalapatis
2026-07-15 15:32 ` [PATCH bpf-next v10 9/9] selftests/bpf: Verify bpf_iter " Leon Hwang
2026-07-17 23:11 ` Emil Tsalapatis
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=9615cf9b-4a77-4d7a-aec4-8990ea6ff638@linux.dev \
--to=leon.hwang@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox