BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Amery Hung <ameryhung@gmail.com>, bpf@vger.kernel.org
Cc: alexei.starovoitov@gmail.com, andrii@kernel.org,
	daniel@iogearbox.net,  memxor@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 14/18] bpf: Check helper mem+size in ARG_PTR_TO_MEM case
Date: Mon, 27 Jul 2026 16:39:34 -0700	[thread overview]
Message-ID: <2fb1dd524daa3d74dcfc007af30f275ed431ce2a.camel@gmail.com> (raw)
In-Reply-To: <20260724190813.1458271-15-ameryhung@gmail.com>

On Fri, 2026-07-24 at 12:08 -0700, Amery Hung wrote:

...

>  kernel/bpf/verifier.c | 16 +++++++---------
>  1 file changed, 7 insertions(+), 9 deletions(-)
> 
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 144c2d8aa492..2326b12a1531 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -8505,9 +8505,6 @@ static int check_func_arg(struct bpf_verifier_env *env, u32 arg,
>  		meta->subprogno = reg->subprogno;
>  		break;
>  	case ARG_PTR_TO_MEM:
> -		/* The access to this pointer is only checked when we hit the
> -		 * next is_mem_size argument below.
> -		 */
>  		if (arg_type & MEM_FIXED_SIZE) {
>  			err = check_mem_reg(env, reg, argno_from_reg(regno), fn->arg_size[arg],
>  					    arg_type & MEM_WRITE ? BPF_WRITE : BPF_READ, meta);
> @@ -8515,14 +8512,15 @@ static int check_func_arg(struct bpf_verifier_env *env, u32 arg,
>  				return err;
>  			if (arg_type & MEM_ALIGNED)
>  				err = check_ptr_alignment(env, reg, 0, fn->arg_size[arg], true);
> +		} else {
> +			struct bpf_reg_state *size_reg = reg_state(env, regno + 1);
> +
> +			err = check_mem_size_reg(env, reg, size_reg, argno,
> +						 argno_from_reg(regno + 1),
> +						 arg_type & MEM_WRITE ? BPF_WRITE : BPF_READ,
> +						 fn->arg_type[arg + 1] & SCALAR_MAYBE_ZERO, meta);
>  		}
>  		break;
> -	case ARG_MEM_SIZE:

Nit:
The ARG_MEM_SIZE would be ignored by this switch after the change, right?
This is a correct thing to do, but I'd be a little bit more defensive.
Let's modify this switch to:
- explicitly skip ARG_MEM_SIZE
- have default clause signalling a verifier error in case of unknown arg type.

> -		err = check_mem_size_reg(env, reg_state(env, regno - 1), reg,
> -					 argno_from_reg(regno - 1), argno,
> -					 fn->arg_type[arg - 1] & MEM_WRITE ? BPF_WRITE : BPF_READ,
> -					 arg_type & SCALAR_MAYBE_ZERO, meta);
> -		break;
>  	case ARG_PTR_TO_DYNPTR:
>  		err = process_dynptr_func(env, reg, argno, insn_idx, arg_type, &meta->ref_obj,
>  					  &meta->dynptr);

  parent reply	other threads:[~2026-07-27 23:39 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 19:07 [PATCH bpf-next v2 00/18] Generate bpf_func_proto for kfunc Amery Hung
2026-07-24 19:07 ` [PATCH bpf-next v2 01/18] bpf: Drop process_timer_func wrappers Amery Hung
2026-07-25  1:39   ` Eduard Zingerman
2026-07-24 19:07 ` [PATCH bpf-next v2 02/18] bpf: Unify const map ptr argument checking for helpers and kfuncs Amery Hung
2026-07-24 19:28   ` sashiko-bot
2026-07-24 20:49     ` Amery Hung
2026-07-24 21:29       ` Kumar Kartikeya Dwivedi
2026-07-25  1:57   ` Eduard Zingerman
2026-07-24 19:07 ` [PATCH bpf-next v2 03/18] bpf: Split kfunc map argument into __const_map and __map Amery Hung
     [not found]   ` <015164cfd5ac0c3bae007313c3859fef6a583233.camel@gmail.com>
2026-07-27 16:48     ` Eduard Zingerman
2026-07-24 19:07 ` [PATCH bpf-next v2 04/18] bpf: Pass kfunc meta to mem and mem_size check Amery Hung
2026-07-27 18:37   ` Eduard Zingerman
2026-07-24 19:07 ` [PATCH bpf-next v2 05/18] bpf: Check helper and kfunc mem+size arguments identically Amery Hung
2026-07-27 20:39   ` Eduard Zingerman
2026-07-27 20:51   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 06/18] selftests/bpf: Add tests for helper and kfunc mem+size arguments Amery Hung
2026-07-24 19:25   ` sashiko-bot
2026-07-27 20:40   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 07/18] bpf: Check fixed-size mem args of helpers and kfuncs the same way Amery Hung
2026-07-24 19:32   ` sashiko-bot
2026-07-24 20:39     ` Amery Hung
2026-07-27 21:17   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 08/18] bpf: Express ARG_CONST_SIZE_OR_ZERO as ARG_CONST_SIZE | SCALAR_MAYBE_ZERO Amery Hung
2026-07-27 22:29   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 09/18] bpf: Rename ARG_CONST_SIZE{,_OR_ZERO} to ARG_MEM_SIZE{,_OR_ZERO} Amery Hung
2026-07-24 19:08 ` [PATCH bpf-next v2 10/18] bpf: Fold __szk const size handling into the scalar arg path Amery Hung
2026-07-27 22:48   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 11/18] bpf: Classify kfunc mem_size args from BTF without register state Amery Hung
2026-07-24 19:38   ` sashiko-bot
2026-07-24 22:52     ` Amery Hung
2026-07-27 22:50   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 12/18] bpf: Handle NULL kfunc pointer args without a KF_ARG_PTR_TO_NULL type Amery Hung
2026-07-27 23:15   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 13/18] bpf: Distinguish fixed- and variable-size kfunc mem args with MEM_FIXED_SIZE Amery Hung
2026-07-27 23:30   ` Eduard Zingerman
2026-07-24 19:08 ` [PATCH bpf-next v2 14/18] bpf: Check helper mem+size in ARG_PTR_TO_MEM case Amery Hung
2026-07-24 19:47   ` sashiko-bot
2026-07-24 21:10     ` Amery Hung
2026-07-27 23:39   ` Eduard Zingerman [this message]
2026-07-24 19:08 ` [PATCH bpf-next v2 15/18] bpf: Classify kfunc pointer arguments from BTF, resolve type against the register Amery Hung
2026-07-24 19:08 ` [PATCH bpf-next v2 16/18] bpf: Tag nullable kfunc pointer args with PTR_MAYBE_NULL Amery Hung
2026-07-24 19:38   ` sashiko-bot
2026-07-24 19:08 ` [PATCH bpf-next v2 17/18] bpf: Classify scalar kfunc arguments from BTF Amery Hung
2026-07-24 19:08 ` [PATCH bpf-next v2 18/18] bpf: Generate kfunc argument prototype at add-call time Amery Hung

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=2fb1dd524daa3d74dcfc007af30f275ed431ce2a.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=memxor@gmail.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