BPF List
 help / color / mirror / Atom feed
From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Puranjay Mohan <puranjay@kernel.org>, bpf@vger.kernel.org
Cc: Puranjay Mohan <puranjay12@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/5] bpf: Add KF_ACQUIRE and KF_RELEASE support for iterators
Date: Thu, 19 Feb 2026 17:45:19 +0000	[thread overview]
Message-ID: <41b15342-0783-4605-877e-d525e6b980f8@gmail.com> (raw)
In-Reply-To: <20260218182555.1501495-2-puranjay@kernel.org>

On 2/18/26 18:25, Puranjay Mohan wrote:
> Some iterators hold resources (like mmap_lock in task_vma) that prevent
> sleeping. To allow BPF programs to release such resources mid-iteration
> and call sleepable helpers, the verifier needs to track acquire/release
> semantics on iterator _next pointers.
>
> Repurpose the st->id field on STACK_ITER slots to track the ref_obj_id
> of the pointer returned by _next when the kfunc is annotated with
> KF_ACQUIRE. This is safe because st->id is initialized to 0 by
> __mark_reg_known_zero() in mark_stack_slots_iter() and is not compared
> in stacksafe() for STACK_ITER slots.
>
> The lifecycle is:
>
>    _next (KF_ACQUIRE):
>      - auto-release old ref if st->id != 0
>      - acquire new ref, store ref_obj_id in st->id
>      - DRAINED branch: release via st->id, set st->id = 0
>      - ACTIVE branch: keeps ref, st->id tracks it
>
>    _release (KF_RELEASE + __iter arg):
>      - read st->id, release_reference(), set st->id = 0
>
>    _destroy:
>      - release st->id if non-zero before releasing iterator's own ref
>
> Signed-off-by: Puranjay Mohan <puranjay@kernel.org>
> ---
>   kernel/bpf/verifier.c | 67 ++++++++++++++++++++++++++++++++++++++++---
>   1 file changed, 63 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 0162f946032f..aa48180b6073 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -355,6 +355,11 @@ struct bpf_kfunc_call_arg_meta {
>   		u8 spi;
>   		u8 frameno;
>   	} iter;
> +	/* Set when a kfunc takes an __iter arg. Used by the KF_RELEASE
For new comments we use kernel style with /* on the first line and then 
your text goes to the next line.
> +	 * path to release the reference tracked on the iterator slot
> +	 * (st->id) instead of requiring a refcounted PTR_TO_BTF_ID arg.
> +	 */
> +	bool has_iter_arg;
>   	struct bpf_map_desc map;
>   	u64 mem_size;
>   };
> @@ -1083,6 +1088,22 @@ static int mark_stack_slots_iter(struct bpf_verifier_env *env,
>   	return 0;
>   }
>   
> +/* Release the acquired reference tracked by iter_st->id, if any.
> + * Used during auto-release in _next, DRAINED handling, and _destroy.
> + */
> +static int iter_release_acquired_ref(struct bpf_verifier_env *env,
> +				     struct bpf_reg_state *iter_st)
> +{
> +	int err;
> +
> +	if (!iter_st->id)
> +		return 0;
> +	err = release_reference(env, iter_st->id);
> +	if (!err)
> +		iter_st->id = 0;
> +	return err;
> +}
> +
>   static int unmark_stack_slots_iter(struct bpf_verifier_env *env,
>   				   struct bpf_reg_state *reg, int nr_slots)
>   {
> @@ -1097,8 +1118,13 @@ static int unmark_stack_slots_iter(struct bpf_verifier_env *env,
>   		struct bpf_stack_state *slot = &state->stack[spi - i];
>   		struct bpf_reg_state *st = &slot->spilled_ptr;
>   
> -		if (i == 0)
> +		if (i == 0) {
> +			/* Release any outstanding acquired ref tracked by
> +			 * st->id before releasing the iterator's own ref.
> +			 */
> +			WARN_ON_ONCE(iter_release_acquired_ref(env, st));
>   			WARN_ON_ONCE(release_reference(env, st->ref_obj_id));
> +		}
>   
>   		__mark_reg_not_init(env, st);
>   
> @@ -8943,6 +8969,7 @@ static int process_iter_arg(struct bpf_verifier_env *env, int regno, int insn_id
>   		/* remember meta->iter info for process_iter_next_call() */
>   		meta->iter.spi = spi;
>   		meta->iter.frameno = reg->frameno;
> +		meta->has_iter_arg = true;
>   		meta->ref_obj_id = iter_ref_obj_id(env, reg, spi);
>   
>   		if (is_iter_destroy_kfunc(meta)) {
> @@ -9178,8 +9205,10 @@ static int process_iter_next_call(struct bpf_verifier_env *env, int insn_idx,
>   	/* mark current iter state as drained and assume returned NULL */
>   	cur_iter->iter.state = BPF_ITER_STATE_DRAINED;
>   	__mark_reg_const_zero(env, &cur_fr->regs[BPF_REG_0]);
> -
> -	return 0;
> +	/* If _next acquired a ref (KF_ACQUIRE), release it in the DRAINED
> +	 * branch since NULL was returned.
> +	 */
> +	return iter_release_acquired_ref(env, cur_iter);
>   }
>   
>   static bool arg_type_is_mem_size(enum bpf_arg_type type)
> @@ -13797,7 +13826,7 @@ static int check_kfunc_args(struct bpf_verifier_env *env, struct bpf_kfunc_call_
>   		}
>   	}
>   
> -	if (is_kfunc_release(meta) && !meta->release_regno) {
> +	if (is_kfunc_release(meta) && !meta->release_regno && !meta->has_iter_arg) {
>   		verbose(env, "release kernel function %s expects refcounted PTR_TO_BTF_ID\n",
>   			func_name);
>   		return -EINVAL;
> @@ -14205,6 +14234,21 @@ static int check_kfunc_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
>   		}
>   		if (err)
>   			return err;
> +	} else if (meta.has_iter_arg && is_kfunc_release(&meta)) {
> +		/* For KF_RELEASE kfuncs taking an __iter arg, release the
> +		 * reference tracked by st->id on the iterator slot.
> +		 */
> +		struct bpf_reg_state *iter_st;
> +
> +		iter_st = get_iter_from_state(env->cur_state, &meta);
> +		if (!iter_st->id) {
> +			verbose(env, "no acquired reference to release\n");
> +			return -EINVAL;
> +		}
> +		err = release_reference(env, iter_st->id);
> +		if (err)
> +			return err;
> +		iter_st->id = 0;
>   	}
>   
>   	if (meta.func_id == special_kfunc_list[KF_bpf_list_push_front_impl] ||
> @@ -14356,6 +14400,18 @@ static int check_kfunc_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
>   			regs[BPF_REG_0].id = ++env->id_gen;
>   		}
>   		mark_btf_func_reg_size(env, BPF_REG_0, sizeof(void *));
> +		/* For iterators with KF_ACQUIRE, auto-release the previous
> +		 * iteration's ref before acquiring a new one, and after
> +		 * acquisition track the new ref on the iter slot.
> +		 */
> +		struct bpf_reg_state *iter_acquire_st = NULL;
This variable declaration shouldn't probably be here.
> +
> +		if (is_iter_next_kfunc(&meta) && is_kfunc_acquire(&meta)) {
> +			iter_acquire_st = get_iter_from_state(env->cur_state, &meta);
> +			err = iter_release_acquired_ref(env, iter_acquire_st);
The acquire and release paths for iterator references in
check_kfunc_call() are far apart, which makes the lifecycle
hard to follow. The guard conditions are also asymmetric:
meta.has_iter_arg for release vs is_iter_next_kfunc() for acquire.

More broadly, could iterator release be unified into the release_regno
dispatch, similar to dynptrs? E.g., set meta->release_regno in
process_iter_arg(), then add an iterator sub-case inside the
if (meta.release_regno) block, keeping all release logic in one
place.
> +			if (err)
> +				return err;
> +		}
>   		if (is_kfunc_acquire(&meta)) {
>   			int id = acquire_reference(env, insn_idx);
>   
> @@ -14368,6 +14424,9 @@ static int check_kfunc_call(struct bpf_verifier_env *env, struct bpf_insn *insn,
>   			ref_set_non_owning(env, &regs[BPF_REG_0]);
>   		}
>   
> +		if (iter_acquire_st)
> +			iter_acquire_st->id = regs[BPF_REG_0].ref_obj_id;
> +
>   		if (reg_may_point_to_spin_lock(&regs[BPF_REG_0]) && !regs[BPF_REG_0].id)
>   			regs[BPF_REG_0].id = ++env->id_gen;
>   	} else if (btf_type_is_void(t)) {
Have you explored marking iter_next as both KF_ACQUIRE and KF_RELEASE,
so the auto-release of the previous iteration's ref hits the existing
release path naturally?
I understand it doesn't work as-is - the release branch errors out
on the first _next call, also last call does not do acquire.
But maybe there is a clean solution.

  reply	other threads:[~2026-02-19 17:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18 18:25 [PATCH bpf-next 0/5] Introduce KF_FORBID_SLEEP modifier for acquire/release kfuncs Puranjay Mohan
2026-02-18 18:25 ` [PATCH bpf-next 1/5] bpf: Add KF_ACQUIRE and KF_RELEASE support for iterators Puranjay Mohan
2026-02-19 17:45   ` Mykyta Yatsenko [this message]
2026-02-19 20:37   ` Eduard Zingerman
2026-02-20  1:05     ` Puranjay Mohan
2026-02-20  1:09       ` Eduard Zingerman
2026-02-18 18:25 ` [PATCH bpf-next 2/5] bpf: Add KF_FORBID_SLEEP modifier for KF_ACQUIRE kfuncs Puranjay Mohan
2026-02-19  3:24   ` Alexei Starovoitov
2026-02-20  0:14     ` Puranjay Mohan
2026-02-19 22:19   ` Eduard Zingerman
2026-02-20  0:51     ` Puranjay Mohan
2026-02-18 18:25 ` [PATCH bpf-next 3/5] bpf: Move locking to bpf_iter_task_vma_next() Puranjay Mohan
2026-02-18 18:25 ` [PATCH bpf-next 4/5] bpf: Add split iteration support to task_vma iterator Puranjay Mohan
2026-02-18 18:25 ` [PATCH bpf-next 5/5] selftests/bpf: Add tests for split " Puranjay Mohan

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=41b15342-0783-4605-877e-d525e6b980f8@gmail.com \
    --to=mykyta.yatsenko5@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@kernel.org \
    --cc=memxor@gmail.com \
    --cc=puranjay12@gmail.com \
    --cc=puranjay@kernel.org \
    /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