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 v6 bpf-next 05/17] selftests/bpf: add selftests for new insn_array map
Date: Wed, 22 Oct 2025 14:06:56 +0000	[thread overview]
Message-ID: <aPjlANnS+hj09w2s@mail.gmail.com> (raw)
In-Reply-To: <0e98a654792b6ab8002b0cf7ddf604e20b2f8f5e.camel@gmail.com>

On 25/10/22 06:55AM, Eduard Zingerman wrote:
> On Wed, 2025-10-22 at 13:44 +0000, Anton Protopopov wrote:
> > On 25/10/21 04:51PM, Eduard Zingerman wrote:
> > > On Sun, 2025-10-19 at 20:21 +0000, Anton Protopopov wrote:
> > > > Add the following selftests for new insn_array map:
> > > > 
> > > >   * Incorrect instruction indexes are rejected
> > > >   * Two programs can't use the same map
> > > >   * BPF progs can't operate the map
> > > >   * no changes to code => map is the same
> > > >   * expected changes when instructions are added
> > > >   * expected changes when instructions are deleted
> > > >   * expected changes when multiple functions are present
> > > > 
> > > > Signed-off-by: Anton Protopopov <a.s.protopopov@gmail.com>
> > > > ---
> > > 
> > > Acked-by: Eduard Zingerman <eddyz87@gmail.com>
> > > 
> > > >  .../selftests/bpf/prog_tests/bpf_insn_array.c | 404 ++++++++++++++++++
> > > >  1 file changed, 404 insertions(+)
> > > >  create mode 100644 tools/testing/selftests/bpf/prog_tests/bpf_insn_array.c
> > > > 
> > > > diff --git a/tools/testing/selftests/bpf/prog_tests/bpf_insn_array.c b/tools/testing/selftests/bpf/prog_tests/bpf_insn_array.c
> > > > new file mode 100644
> > > > index 000000000000..a4304ef5be13
> > > > --- /dev/null
> > > > +++ b/tools/testing/selftests/bpf/prog_tests/bpf_insn_array.c
> > > 
> > > [...]
> > > 
> > > > +static void check_bpf_no_lookup(void)
> > > 
> > > This one can be moved to prog_tests/bpf_insn_array.c, I think.
> > 
> > A typo? (This is a patch for the prog_tests/bpf_insn_array.c)
> 
> Yes, I mean progs/verifier_gotox.c, the one with inline assembly.

I think it should stay here. There will be other usages of the
instruction array, and neither should allow operations on it from
a BPF prog (indirect calls, static keys).

> > 
> > > > +{
> > > > +	struct bpf_insn insns[] = {
> > > > +		BPF_LD_MAP_FD(BPF_REG_1, 0),
> > > > +		BPF_ST_MEM(BPF_DW, BPF_REG_10, -8, 0),
> > > > +		BPF_MOV64_REG(BPF_REG_2, BPF_REG_10),
> > > > +		BPF_ALU64_IMM(BPF_ADD, BPF_REG_2, -8),
> > > > +		BPF_RAW_INSN(BPF_JMP | BPF_CALL, 0, 0, 0, BPF_FUNC_map_lookup_elem),
> > > > +		BPF_EXIT_INSN(),
> > > > +	};
> > > > +	int prog_fd = -1, map_fd;
> > > > +
> > > > +	map_fd = map_create(BPF_MAP_TYPE_INSN_ARRAY, 1);
> > > > +	if (!ASSERT_GE(map_fd, 0, "map_create"))
> > > > +		return;
> > > > +
> > > > +	insns[0].imm = map_fd;
> > > > +
> > > > +	if (!ASSERT_EQ(bpf_map_freeze(map_fd), 0, "bpf_map_freeze"))
> > > > +		goto cleanup;
> > > > +
> > > > +	prog_fd = prog_load(insns, ARRAY_SIZE(insns), NULL, 0);
> > > > +	if (!ASSERT_EQ(prog_fd, -EINVAL, "program should have been rejected (prog_fd != -EINVAL)"))
> > > > +		goto cleanup;
> > > > +
> > > > +	/* correctness: check that prog is still loadable with normal map */
> > > > +	close(map_fd);
> > > > +	map_fd = map_create(BPF_MAP_TYPE_ARRAY, 1);
> > > > +	insns[0].imm = map_fd;
> > > > +	prog_fd = prog_load(insns, ARRAY_SIZE(insns), NULL, 0);
> > > > +	if (!ASSERT_GE(prog_fd, 0, "bpf(BPF_PROG_LOAD)"))
> > > > +		goto cleanup;
> > > > +
> > > > +cleanup:
> > > > +	close(prog_fd);
> > > > +	close(map_fd);
> > > > +}
> > > 
> > > [...]

  reply	other threads:[~2025-10-22 14:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-19 20:21 [PATCH v6 bpf-next 00/17] BPF indirect jumps Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 01/17] bpf: fix the return value of push_stack Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 02/17] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 03/17] bpf: generalize and export map_get_next_key for arrays Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 04/17] bpf, x86: add new map type: instructions array Anton Protopopov
2025-10-21 17:49   ` Alexei Starovoitov
2025-10-21 18:32     ` Anton Protopopov
2025-10-21 23:26   ` Eduard Zingerman
2025-10-24 12:12     ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 05/17] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-10-21 23:51   ` Eduard Zingerman
2025-10-22 13:44     ` Anton Protopopov
2025-10-22 13:55       ` Eduard Zingerman
2025-10-22 14:06         ` Anton Protopopov [this message]
2025-10-22 14:03           ` Eduard Zingerman
2025-10-22 14:13             ` Anton Protopopov
2025-10-22 17:00             ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 06/17] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 07/17] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 08/17] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-10-20  8:38   ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 09/17] bpf: make bpf_insn_successors to return a pointer Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 10/17] bpf, x86: add support for indirect jumps Anton Protopopov
2025-10-20  7:23   ` Anton Protopopov
2025-10-21 21:17   ` Eduard Zingerman
2025-10-22  6:51     ` Anton Protopopov
2025-10-22  6:53       ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 11/17] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-10-21 21:19   ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 12/17] bpf, docs: do not state that indirect jumps are not supported Anton Protopopov
2025-10-21 19:15   ` Eduard Zingerman
2025-10-21 19:32     ` Anton Protopopov
2025-10-21 19:36       ` Eduard Zingerman
2025-10-21 19:50         ` Anton Protopopov
2025-10-21 20:17           ` Eduard Zingerman
2025-10-19 20:21 ` [PATCH v6 bpf-next 13/17] libbpf: fix formatting of bpf_object__append_subprog_code Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 14/17] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-10-21 22:18   ` Eduard Zingerman
2025-10-21 22:45     ` Eduard Zingerman
2025-10-24 12:52     ` Anton Protopopov
2025-10-25 17:39       ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 15/17] bpftool: Recognize insn_array map type Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 16/17] selftests/bpf: add new verifier_gotox test Anton Protopopov
2025-10-21 22:42   ` Eduard Zingerman
2025-10-24 11:40     ` Anton Protopopov
2025-10-26 12:34       ` Anton Protopopov
2025-10-27 23:11         ` Eduard Zingerman
2025-10-28 12:06           ` Anton Protopopov
2025-10-19 20:21 ` [PATCH v6 bpf-next 17/17] selftests/bpf: add C-level selftests for indirect jumps Anton Protopopov
2025-10-22  0:27   ` Eduard Zingerman
2025-10-22 13:34     ` Anton Protopopov
2025-10-25 17:41       ` Anton Protopopov
2025-10-21 18:30 ` [PATCH v6 bpf-next 00/17] BPF " patchwork-bot+netdevbpf

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=aPjlANnS+hj09w2s@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.