All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: 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 08/11] bpf, x86: add support for indirect jumps
Date: Thu, 28 Aug 2025 14:15:11 +0000	[thread overview]
Message-ID: <aLBkbzahReym9UXm@mail.gmail.com> (raw)
In-Reply-To: <aLAoUK22+PpuAbhy@mail.gmail.com>

On 25/08/28 09:58AM, Anton Protopopov wrote:
> On 25/08/25 04:15PM, Eduard Zingerman wrote:
> > On Sat, 2025-08-16 at 18:06 +0000, Anton Protopopov wrote:
> > 
> 

[...]

> > >  
> > > -static int insn_successors(struct bpf_prog *prog, u32 idx, u32 succ[2])
> > > +static int insn_successors_regular(struct bpf_prog *prog, u32 insn_idx, u32 *succ)
> > >  {
> > > -	struct bpf_insn *insn = &prog->insnsi[idx];
> > > +	struct bpf_insn *insn = &prog->insnsi[insn_idx];
> > >  	int i = 0, insn_sz;
> > >  	u32 dst;
> > >  
> > >  	insn_sz = bpf_is_ldimm64(insn) ? 2 : 1;
> > > -	if (can_fallthrough(insn) && idx + 1 < prog->len)
> > > -		succ[i++] = idx + insn_sz;
> > > +	if (can_fallthrough(insn) && insn_idx + 1 < prog->len)
> > > +		succ[i++] = insn_idx + insn_sz;
> > >  
> > >  	if (can_jump(insn)) {
> > > -		dst = idx + jmp_offset(insn) + 1;
> > > +		dst = insn_idx + jmp_offset(insn) + 1;
> > >  		if (i == 0 || succ[0] != dst)
> > >  			succ[i++] = dst;
> > >  	}
> > > @@ -24194,6 +24605,36 @@ static int insn_successors(struct bpf_prog *prog, u32 idx, u32 succ[2])
> > >  	return i;
> > >  }
> > >  
> > > +static int insn_successors_gotox(struct bpf_verifier_env *env,
> > > +				 struct bpf_prog *prog,
> > > +				 u32 insn_idx, u32 **succ)
> > > +{
> > > +	struct jt *jt = &env->insn_aux_data[insn_idx].jt;
> > > +
> > > +	if (WARN_ON_ONCE(!jt->off || !jt->off_cnt))
> > > +		return -EFAULT;
> > > +
> > > +	*succ = jt->off;
> > > +	return jt->off_cnt;
> > > +}
> > > +
> > > +/*
> > > + * Fill in *succ[0],...,*succ[n-1] with successors. The default *succ
> > > + * pointer (of size 2) may be replaced with a custom one if more
> > > + * elements are required (i.e., an indirect jump).
> > > + */
> > > +static int insn_successors(struct bpf_verifier_env *env,
> > > +			   struct bpf_prog *prog,
> > > +			   u32 insn_idx, u32 **succ)
> > > +{
> > > +	struct bpf_insn *insn = &prog->insnsi[insn_idx];
> > > +
> > > +	if (unlikely(insn_is_gotox(insn)))
> > > +		return insn_successors_gotox(env, prog, insn_idx, succ);
> > > +
> > > +	return insn_successors_regular(prog, insn_idx, *succ);
> > > +}
> > > +
> > 
> > The `prog` parameter can be dropped, as it is accessible from `env`.
> > I don't like the `u32 **succ` part of this interface.
> > What about one of the following alternatives:
> > 
> > - u32 *insn_successors(struct bpf_verifier_env *env, u32 insn_idx)
> >   and `u32 succ_buf[2]` added to bpf_verifier_env?
> 
> I like this variant of yours more than the second one.
> 
> Small corrections that this would be
> 
>     u32 *insn_successors(struct bpf_verifier_env *env, u32 insn_idx, int *succ_num)
> 
> to return the number of instructions.
> 
> > - int insn_successor(struct bpf_verifier_env *env, u32 insn_idx, u32 succ_num):
> > 	bool fallthrough = can_fallthrough(insn);
> > 	bool jump = can_jump(insn);
> > 	if (succ_num == 0) {
> > 		if (fallthrough)
> > 			return <next insn>
> > 		if (jump)
> > 			return <jump tgt>
> > 	} else if (succ_num == 1) {
> > 		if (fallthrough && jump)
> > 			return <jmp tgt>
> > 	} else if (is_gotox) {
> > 		return <lookup>
> > 	}
> > 	return -1;
> >   
> > ?

So, insn_successors() actually returns two values: a pointer and a
number elements. This is the same value as "struct bpf_jt" (struct jt
in the sent patch). Wdyt about 

     struct bpf_jt *insn_successors(struct bpf_verifier_env *env, u32 insn_idx)

? (Maybe bpf_jt is not right name here, "insn_array" is already used
in the map, maybe smth with "successors"?)

  reply	other threads:[~2025-08-28 14:09 UTC|newest]

Thread overview: 43+ 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
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  0:35   ` kernel test robot
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 [this message]
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-09-13 19:38     ` 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
2025-09-04 20:27 ` [PATCH v1 bpf-next 00/11] BPF " Yonghong Song
2025-09-05  8:20   ` Anton Protopopov
2025-09-05 15:39     ` 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=aLBkbzahReym9UXm@mail.gmail.com \
    --to=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=eddyz87@gmail.com \
    --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 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.