From: Eduard Zingerman <eddyz87@gmail.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>, bpf@vger.kernel.org
Cc: Nicholas Carlini <npc@anthropic.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Emil Tsalapatis <emil@etsalapatis.com>,
kkd@meta.com, kernel-team@meta.com
Subject: Re: [PATCH bpf v3 6/7] bpf: Assign lock identity to callback map values
Date: Mon, 14 Sep 2026 12:33:56 -0700 [thread overview]
Message-ID: <e1f1e90cf0c461bd2137cd64edc0e24806045e88.camel@gmail.com> (raw)
In-Reply-To: <20260914131701.2529725-7-memxor@gmail.com>
On Mon, 2026-09-14 at 15:16 +0200, Kumar Kartikeya Dwivedi wrote:
> A nested bpf_for_each_map_elem() callback can unlock a different element
> of the same map:
>
> static long inner(void *map, int *key, struct value *v,
> struct value **outer_value)
> {
> bpf_spin_lock(&v->lock);
> bpf_spin_unlock(&(*outer_value)->lock);
> return 0;
> }
>
> static long outer(void *map, int *key, struct value *v, void *ctx)
> {
> bpf_for_each_map_elem(map, inner, &v, 0);
> return 0;
> }
>
> Both callback values currently have ID zero and the same map_ptr.
> process_spin_lock() compares those two fields, so it accepts the unlock
> even though the two callbacks can receive different map elements.
>
> Assign a fresh ID to every callback map value in the for-each,
> timer/workqueue, and task-work constructors. Copies of one callback
> argument retain its ID, so locking and unlocking through that argument
> continues to work. Distinct callbacks also get distinct IDs for
> single-element arrays, including inner arrays sharing inner_map_meta.
>
> Preserve map_uid for every inner-map lookup and compare it through
> check_ids() during state pruning. This preserves relationships between
> maps, keys, and values while allowing equivalent states with different
> lookup IDs to match. It avoids field-specific rules for when an inner map
> needs an identity.
>
> Move map_uid out of the metadata union and next to the other IDs, so
> register comparisons can use the existing memcmp() ranges and remap the
> IDs separately. Clear it when resetting a register or converting a map
> lookup result to a socket pointer. Shrink frameno to u8, which is enough
> for MAX_CALL_FRAMES, to make room without growing bpf_reg_state.
>
> Fixes: d0d78c1df9b1 ("bpf: Allow locking bpf_spin_lock global variables")
> Reported-by: Nicholas Carlini <npc@anthropic.com>
> Suggested-by: Nicholas Carlini <npc@anthropic.com>
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
It appears all map_uid has to be reset are handled.
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index ddba53eaa333..ab4f0ea2647b 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
...
> @@ -1925,17 +1926,18 @@ static void refine_map_lookup_value(struct bpf_reg_state *reg)
> if (map->inner_map_meta) {
> reg->type = CONST_PTR_TO_MAP | maybe_null;
> reg->map_ptr = map->inner_map_meta;
> - /* transfer reg's id which is unique for every map_lookup_elem
> - * as UID of the inner map.
> + /*
> + * Each lookup gets a unique ID. Preserve it as the inner map's
> + * identity, since different inner maps share inner_map_meta.
> */
Nit: old comment is better, imo.
> - if (btf_record_has_field(map->inner_map_meta->record,
> - BPF_TIMER | BPF_WORKQUEUE | BPF_TASK_WORK))
> - reg->map_uid = reg->id;
> + reg->map_uid = reg->id;
> } else if (map->map_type == BPF_MAP_TYPE_XSKMAP) {
> reg->type = PTR_TO_XDP_SOCK | maybe_null;
> + reg->map_uid = 0;
> } else if (map->map_type == BPF_MAP_TYPE_SOCKMAP ||
> map->map_type == BPF_MAP_TYPE_SOCKHASH) {
> reg->type = PTR_TO_SOCKET | maybe_null;
> + reg->map_uid = 0;
> }
> }
>
...
next prev parent reply other threads:[~2026-09-14 19:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:16 [PATCH bpf v3 0/7] Misc bug fixes - part 5 Kumar Kartikeya Dwivedi
2026-09-14 13:16 ` [PATCH bpf v3 1/7] bpf: Make post-verification instruction rewrites killable Kumar Kartikeya Dwivedi
2026-09-14 14:30 ` bot+bpf-ci
2026-09-14 18:52 ` Eduard Zingerman
2026-09-14 13:16 ` [PATCH bpf v3 2/7] bpf: Preserve packet pointer class displacement in regsafe() Kumar Kartikeya Dwivedi
2026-09-14 14:30 ` bot+bpf-ci
2026-09-14 18:53 ` Eduard Zingerman
2026-09-14 13:16 ` [PATCH bpf v3 3/7] selftests/bpf: Test packet pointer class displacement pruning Kumar Kartikeya Dwivedi
2026-09-14 13:16 ` [PATCH bpf v3 4/7] bpf: Restrict CO-RE poisoning to relocatable instructions Kumar Kartikeya Dwivedi
2026-09-14 14:08 ` sashiko-bot
2026-09-14 14:15 ` bot+bpf-ci
2026-09-14 20:13 ` Eduard Zingerman
2026-09-14 19:54 ` Andrii Nakryiko
2026-09-14 20:21 ` Alexei Starovoitov
2026-09-14 20:42 ` Kumar Kartikeya Dwivedi
2026-09-14 21:02 ` Andrii Nakryiko
2026-09-14 20:09 ` Eduard Zingerman
2026-09-14 13:16 ` [PATCH bpf v3 5/7] selftests/bpf: Test CO-RE instruction poisoning restrictions Kumar Kartikeya Dwivedi
2026-09-14 14:30 ` bot+bpf-ci
2026-09-14 20:46 ` Eduard Zingerman
2026-09-14 13:16 ` [PATCH bpf v3 6/7] bpf: Assign lock identity to callback map values Kumar Kartikeya Dwivedi
2026-09-14 14:30 ` bot+bpf-ci
2026-09-14 19:33 ` Eduard Zingerman [this message]
2026-09-14 13:16 ` [PATCH bpf v3 7/7] selftests/bpf: Check callback map value lock identity Kumar Kartikeya Dwivedi
2026-09-14 14:45 ` bot+bpf-ci
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=e1f1e90cf0c461bd2137cd64edc0e24806045e88.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=emil@etsalapatis.com \
--cc=kernel-team@meta.com \
--cc=kkd@meta.com \
--cc=memxor@gmail.com \
--cc=npc@anthropic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox