From: Eduard Zingerman <eddyz87@gmail.com>
To: Yonghong Song <yonghong.song@linux.dev>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next v4 04/13] bpf: Track R2 of register-pair returns in precision backtracking
Date: Wed, 12 Aug 2026 14:16:16 -0700 [thread overview]
Message-ID: <6e48cbadf7fb90cce2da403266e4a962928b7c88.camel@gmail.com> (raw)
In-Reply-To: <20260811000932.2381351-1-yonghong.song@linux.dev>
On Mon, 2026-08-10 at 17:09 -0700, Yonghong Song wrote:
...
> diff --git a/include/linux/bpf_verifier.h b/include/linux/bpf_verifier.h
> index 79680f3b4c74..911d57ce2488 100644
> --- a/include/linux/bpf_verifier.h
> +++ b/include/linux/bpf_verifier.h
> @@ -1447,6 +1447,8 @@ int bpf_jmp_offset(struct bpf_insn *insn);
> struct bpf_iarray *bpf_insn_successors(struct bpf_verifier_env *env, u32 idx);
> void bpf_fmt_stack_mask(char *buf, ssize_t buf_sz, u64 stack_mask);
> bool bpf_subprog_is_global(const struct bpf_verifier_env *env, int subprog);
> +int bpf_get_kfunc_ret_size(const struct bpf_prog *prog, u32 func_id,
> + u16 btf_fd_idx, u8 *ret_size);
>
> int bpf_find_subprog(struct bpf_verifier_env *env, int off);
> bool bpf_is_throw_kfunc(struct bpf_insn *insn);
> diff --git a/kernel/bpf/backtrack.c b/kernel/bpf/backtrack.c
> index 40bd04421a99..fc8ecad6f01b 100644
> --- a/kernel/bpf/backtrack.c
> +++ b/kernel/bpf/backtrack.c
> @@ -425,6 +425,15 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
> */
> verifier_bug_if(idx + 1 != subseq_idx, env,
> "extra insn from subprog");
> + /*
> + * a global subprog returning more than 8 bytes
> + * sets R2 as well. R2 is part of the args mask
> + * checked just below, so it has to be cleared
> + * here rather than next to R0.
> + */
> + if (bt_is_reg_set(bt, BPF_REG_2) &&
> + bpf_ret_reg_pair(env, subprog))
> + bt_clear_reg(bt, BPF_REG_2);
Nit: Tbh, I don't see a need in the bpf_ret_reg_pair() check.
I'd call bt_clear_reg(r2) unconditionally.
Don't find verifier_bug() justification all that compelling.
> /* r1-r5 are invalidated after subprog call,
> * so for global func call it shouldn't be set
> * anymore
> @@ -508,6 +517,19 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
> return -ENOTSUPP;
> /* regular helper call sets R0 */
> bt_clear_reg(bt, BPF_REG_0);
> + /* a kfunc returning more than 8 bytes also sets R2 */
> + if (insn->src_reg == BPF_PSEUDO_KFUNC_CALL &&
> + bt_is_reg_set(bt, BPF_REG_2)) {
> + u8 ret_size;
> + int err;
> +
> + err = bpf_get_kfunc_ret_size(env->prog, insn->imm, insn->off,
> + &ret_size);
> + if (verifier_bug_if(err, env, "no kfunc desc for insn %d", idx))
> + return -EFAULT;
> + if (ret_size > 8)
> + bt_clear_reg(bt, BPF_REG_2);
> + }
And same here, too much code for bug detection that fired once or
twice in my memory.
> if (bt_reg_mask(bt) & BPF_REGMASK_ARGS) {
> /* if backtracking was looking for registers R1-R5
> * they should have been found already.
> @@ -522,7 +544,30 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
> return -EFAULT;
> }
> } else if (opcode == BPF_EXIT) {
> - bool r0_precise;
> + bool from_subprog_call, r0_precise, r2_precise = false;
> +
> + /*
> + * BPF_EXIT in subprog or callback always returns
> + * right after the call instruction, so by checking
> + * whether the instruction at subseq_idx-1 is subprog
> + * call or not we can distinguish actual exit from
> + * *subprog* from exit from *callback*. In the former
> + * case, we need to propagate the precision of the
> + * return registers, if necessary. In the latter we
> + * never do that.
> + */
> + from_subprog_call = subseq_idx - 1 >= 0 &&
> + bpf_pseudo_call(&env->prog->insnsi[subseq_idx - 1]);
> + if (from_subprog_call && bt_is_reg_set(bt, BPF_REG_2)) {
> + struct bpf_subprog_info *callee;
> +
> + /* 'idx' is the exit insn, so it is in the callee */
> + callee = bpf_find_containing_subprog(env, idx);
> + if (verifier_bug_if(!callee, env,
> + "no subprog contains exit insn %d", idx))
> + return -EFAULT;
> + r2_precise = bpf_ret_reg_pair(env, callee - env->subprog_info);
> + }
And here, if the verifier_bug check is ignored r0/r2 can be handled together.
>
> /* Backtracking to a nested function call, 'idx' is a part of
> * the inner frame 'subseq_idx' is a part of the outer frame.
...
next prev parent reply other threads:[~2026-08-12 21:16 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 0:09 [PATCH bpf-next v4 00/13] bpf: Support aggregate return values up to 16 bytes Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 01/13] bpf: Factor check_global_ret_scalar_reg() out of the global return check Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 02/13] bpf: Add helpers to describe the R0:R2 return register pair Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 19:31 ` Yonghong Song
2026-08-12 20:07 ` Eduard Zingerman
2026-08-13 18:02 ` Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 03/13] bpf: Wire up JIT support for 16-byte kfunc returns Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 19:48 ` Yonghong Song
2026-08-12 20:42 ` Eduard Zingerman
2026-08-11 0:09 ` [PATCH bpf-next v4 04/13] bpf: Track R2 of register-pair returns in precision backtracking Yonghong Song
2026-08-12 21:16 ` Eduard Zingerman [this message]
2026-08-13 18:04 ` Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 05/13] bpf: Account R2 of register-pair returns in live register analysis Yonghong Song
2026-08-11 1:09 ` bot+bpf-ci
2026-08-12 19:55 ` Yonghong Song
2026-08-12 21:21 ` Eduard Zingerman
2026-08-13 18:05 ` Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 06/13] bpf: Reject callbacks returning more than 8 bytes Yonghong Song
2026-08-12 21:41 ` Eduard Zingerman
2026-08-13 18:09 ` Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 07/13] bpf: Add verifier support for 16-byte returns in R0:R2 Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 20:12 ` Yonghong Song
2026-08-12 22:12 ` Eduard Zingerman
2026-08-13 18:20 ` Yonghong Song
2026-08-14 22:08 ` Eduard Zingerman
2026-08-11 0:09 ` [PATCH bpf-next v4 08/13] bpf: Reject register-pair returns when the subprog BTF is unreliable Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 20:26 ` Yonghong Song
2026-08-12 22:24 ` Eduard Zingerman
2026-08-13 18:22 ` Yonghong Song
2026-08-11 0:09 ` [PATCH bpf-next v4 09/13] bpf: Enable aggregate return types up to 16 bytes Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 20:29 ` Yonghong Song
2026-08-12 22:47 ` Eduard Zingerman
2026-08-13 18:23 ` Yonghong Song
2026-08-11 0:10 ` [PATCH bpf-next v4 10/13] selftests/bpf: Add C tests for 16-byte returns in R0:R2 Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 20:49 ` Yonghong Song
2026-08-12 23:15 ` Eduard Zingerman
2026-08-13 18:24 ` Yonghong Song
2026-08-11 0:10 ` [PATCH bpf-next v4 11/13] selftests/bpf: Add inline-asm and subprog tests for R0:R2 returns Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 21:08 ` Yonghong Song
2026-08-12 23:29 ` Eduard Zingerman
2026-08-13 18:25 ` Yonghong Song
2026-08-13 0:09 ` Eduard Zingerman
2026-08-11 0:10 ` [PATCH bpf-next v4 12/13] selftests/bpf: Add tests for callbacks returning more than 8 bytes Yonghong Song
2026-08-11 1:24 ` bot+bpf-ci
2026-08-12 21:22 ` Yonghong Song
2026-08-13 0:10 ` Eduard Zingerman
2026-08-13 18:27 ` Yonghong Song
2026-08-11 0:10 ` [PATCH bpf-next v4 13/13] Documentation/bpf: Document up to 16-byte kfunc return values in R0:R2 Yonghong Song
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=6e48cbadf7fb90cce2da403266e4a962928b7c88.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=kernel-team@fb.com \
--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 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.