From: Eduard Zingerman <eddyz87@gmail.com>
To: Anton Protopopov <a.s.protopopov@gmail.com>,
bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Anton Protopopov <aspsk@isovalent.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Quentin Monnet <qmo@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH v1 bpf-next 01/11] bpf: fix the return value of push_stack
Date: Mon, 25 Aug 2025 11:12:01 -0700 [thread overview]
Message-ID: <e485c7411db1661d181c238cfb5380b65a3c3ad7.camel@gmail.com> (raw)
In-Reply-To: <20250816180631.952085-2-a.s.protopopov@gmail.com>
On Sat, 2025-08-16 at 18:06 +0000, Anton Protopopov wrote:
The change makes sense to me, please see a few comments below.
[...]
> @@ -2111,12 +2111,12 @@ static struct bpf_verifier_state *push_stack(struct bpf_verifier_env *env,
> env->stack_size++;
> err = copy_verifier_state(&elem->st, cur);
> if (err)
> - return NULL;
> + return ERR_PTR(-ENOMEM);
> elem->st.speculative |= speculative;
> if (env->stack_size > BPF_COMPLEXITY_LIMIT_JMP_SEQ) {
> verbose(env, "The sequence of %d jumps is too complex.\n",
> env->stack_size);
> - return NULL;
> + return ERR_PTR(-EFAULT);
Nit: this should be -E2BIG, I think.
> }
> if (elem->st.parent) {
> ++elem->st.parent->branches;
> @@ -2912,7 +2912,7 @@ static struct bpf_verifier_state *push_async_cb(struct bpf_verifier_env *env,
>
> elem = kzalloc(sizeof(struct bpf_verifier_stack_elem), GFP_KERNEL_ACCOUNT);
> if (!elem)
> - return NULL;
> + return ERR_PTR(-ENOMEM);
>
> elem->insn_idx = insn_idx;
> elem->prev_insn_idx = prev_insn_idx;
> @@ -2924,7 +2924,7 @@ static struct bpf_verifier_state *push_async_cb(struct bpf_verifier_env *env,
> verbose(env,
> "The sequence of %d jumps is too complex for async cb.\n",
> env->stack_size);
> - return NULL;
> + return ERR_PTR(-EFAULT);
(and here too)
> }
> /* Unlike push_stack() do not copy_verifier_state().
> * The caller state doesn't matter.
[...]
> @@ -14217,7 +14217,7 @@ sanitize_speculative_path(struct bpf_verifier_env *env,
> struct bpf_reg_state *regs;
>
> branch = push_stack(env, next_idx, curr_idx, true);
> - if (branch && insn) {
> + if (!IS_ERR(branch) && insn) {
Note: branch returned by `sanitize_speculative_path` is never used.
Maybe change the function to return `int` and do the regular
err = sanitize_speculative_path()
if (err)
return err;
thing here?
> regs = branch->frame[branch->curframe]->regs;
> if (BPF_SRC(insn->code) == BPF_K) {
> mark_reg_unknown(env, regs, insn->dst_reg);
[...]
> @@ -16721,8 +16720,7 @@ static int check_cond_jmp_op(struct bpf_verifier_env *env,
> * execution.
> */
> if (!env->bypass_spec_v1 &&
> - !sanitize_speculative_path(env, insn, *insn_idx + 1,
> - *insn_idx))
> + IS_ERR(sanitize_speculative_path(env, insn, *insn_idx + 1, *insn_idx)))
> return -EFAULT;
I think the error code should be taken from the return value of the
sanitize_speculative_path().
> if (env->log.level & BPF_LOG_LEVEL)
> print_insn_state(env, this_branch, this_branch->curframe);
> @@ -16734,9 +16732,9 @@ static int check_cond_jmp_op(struct bpf_verifier_env *env,
> * simulation under speculative execution.
> */
> if (!env->bypass_spec_v1 &&
> - !sanitize_speculative_path(env, insn,
> - *insn_idx + insn->off + 1,
> - *insn_idx))
> + IS_ERR(sanitize_speculative_path(env, insn,
> + *insn_idx + insn->off + 1,
> + *insn_idx)))
Same here.
> return -EFAULT;
> if (env->log.level & BPF_LOG_LEVEL)
> print_insn_state(env, this_branch, this_branch->curframe);
[...]
next prev parent reply other threads:[~2025-08-25 18:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 18:06 [PATCH v1 bpf-next 00/11] BPF indirect jumps Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 01/11] bpf: fix the return value of push_stack Anton Protopopov
2025-08-25 18:12 ` Eduard Zingerman [this message]
2025-08-26 15:00 ` Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 02/11] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 03/11] bpf, x86: add new map type: instructions array Anton Protopopov
2025-08-25 21:05 ` Eduard Zingerman
2025-08-26 15:52 ` Anton Protopopov
2025-08-26 16:04 ` Eduard Zingerman
2025-08-16 18:06 ` [PATCH v1 bpf-next 04/11] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 05/11] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-08-17 5:50 ` kernel test robot
2025-08-18 8:24 ` Anton Protopopov
2025-08-25 23:29 ` Eduard Zingerman
2025-08-27 9:20 ` Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 06/11] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 07/11] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 08/11] bpf, x86: add support for indirect jumps Anton Protopopov
2025-08-18 7:57 ` Dan Carpenter
2025-08-18 8:22 ` Anton Protopopov
2025-08-25 23:15 ` Eduard Zingerman
2025-08-27 15:34 ` Anton Protopopov
2025-08-27 18:58 ` Eduard Zingerman
2025-08-28 9:58 ` Anton Protopopov
2025-08-28 14:15 ` Anton Protopopov
2025-08-28 16:10 ` Eduard Zingerman
2025-08-28 16:30 ` Eduard Zingerman
2025-08-16 18:06 ` [PATCH v1 bpf-next 09/11] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-08-16 18:06 ` [PATCH v1 bpf-next 10/11] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-08-21 0:20 ` Andrii Nakryiko
2025-08-21 13:05 ` Anton Protopopov
2025-08-21 18:14 ` Andrii Nakryiko
2025-08-21 19:12 ` Anton Protopopov
2025-08-26 0:06 ` Eduard Zingerman
2025-08-26 16:15 ` Anton Protopopov
2025-08-26 16:51 ` Anton Protopopov
2025-08-26 16:47 ` Eduard Zingerman
2025-08-16 18:06 ` [PATCH v1 bpf-next 11/11] selftests/bpf: add selftests for " Anton Protopopov
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=e485c7411db1661d181c238cfb5380b65a3c3ad7.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=a.s.protopopov@gmail.com \
--cc=andrii@kernel.org \
--cc=aspsk@isovalent.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=qmo@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;
as well as URLs for NNTP newsgroup(s).