public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
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 v3 bpf-next 01/13] bpf: fix the return value of push_stack
Date: Thu, 18 Sep 2025 17:17:16 -0700	[thread overview]
Message-ID: <da197caec5cf8d4aed067c94bbb13ed62252ad62.camel@gmail.com> (raw)
In-Reply-To: <20250918093850.455051-2-a.s.protopopov@gmail.com>

On Thu, 2025-09-18 at 09:38 +0000, Anton Protopopov wrote:
> In [1] Eduard mentioned that on push_stack failure verifier code
> should return -ENOMEM instead of -EFAULT. After checking with the
> other call sites I've found that code randomly returns either -ENOMEM
> or -EFAULT. This patch unifies the return values for the push_stack
> (and similar push_async_cb) functions such that error codes are
> always assigned properly.
> 
>   [1] https://lore.kernel.org/bpf/20250615085943.3871208-1-a.s.protopopov@gmail.com
> 
> Signed-off-by: Anton Protopopov <a.s.protopopov@gmail.com>
> ---

Acked-by: Eduard Zingerman <eddyz87@gmail.com>

> @@ -14256,7 +14255,7 @@ sanitize_speculative_path(struct bpf_verifier_env *env,
>  			mark_reg_unknown(env, regs, insn->src_reg);
>  		}
>  	}
> -	return branch;
> +	return IS_ERR(branch) ? PTR_ERR(branch) : 0;

Nit: this is the same as PTR_ERR_OR_ZERO.

>  }
>  
>  static int sanitize_ptr_alu(struct bpf_verifier_env *env,

[...]

  reply	other threads:[~2025-09-19  0:17 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  9:38 [PATCH v3 bpf-next 00/13] BPF indirect jumps Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 01/13] bpf: fix the return value of push_stack Anton Protopopov
2025-09-19  0:17   ` Eduard Zingerman [this message]
2025-09-19  7:18     ` Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 02/13] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 03/13] bpf, x86: add new map type: instructions array Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 04/13] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 05/13] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-09-19  6:35   ` Eduard Zingerman
2025-09-19  7:05     ` Anton Protopopov
2025-09-19  7:12       ` Eduard Zingerman
2025-09-19 18:26         ` Alexei Starovoitov
2025-09-19 19:28           ` Daniel Borkmann
2025-09-19 19:44             ` Eduard Zingerman
2025-09-19 20:27               ` Anton Protopopov
2025-09-19 20:47                 ` Eduard Zingerman
2025-09-22  9:28                   ` Anton Protopopov
2025-09-30  9:07                     ` Anton Protopopov
2025-09-19 21:41               ` Daniel Borkmann
2025-09-18  9:38 ` [PATCH v3 bpf-next 06/13] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 07/13] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-09-19 18:25   ` Eduard Zingerman
2025-09-19 18:38     ` Eduard Zingerman
2025-09-19 19:25       ` Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 08/13] bpf, x86: add support for indirect jumps Anton Protopopov
2025-09-20  0:28   ` Eduard Zingerman
2025-09-21 19:12     ` Eduard Zingerman
2025-09-25 18:07     ` Anton Protopopov
2025-09-29 14:10       ` Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 09/13] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 10/13] libbpf: fix formatting of bpf_object__append_subprog_code Anton Protopopov
2025-09-19 23:18   ` Andrii Nakryiko
2025-09-18  9:38 ` [PATCH v3 bpf-next 11/13] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-09-19 23:18   ` Andrii Nakryiko
2025-09-22 10:13     ` Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 12/13] bpftool: Recognize insn_array map type Anton Protopopov
2025-09-18  9:38 ` [PATCH v3 bpf-next 13/13] selftests/bpf: add selftests for indirect jumps Anton Protopopov
2025-09-20  0:58   ` Eduard Zingerman
2025-09-20 22:27     ` Eduard Zingerman
2025-09-20 22:32       ` Eduard Zingerman
2025-09-25 18:14       ` Anton Protopopov
2025-09-19  6:46 ` [PATCH v3 bpf-next 00/13] BPF " Eduard Zingerman
2025-09-19 14:57   ` Anton Protopopov
2025-09-19 16:49     ` Eduard Zingerman
2025-09-19 17:27   ` Eduard Zingerman
2025-09-19 18:03     ` Eduard Zingerman

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=da197caec5cf8d4aed067c94bbb13ed62252ad62.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