From: Paul Chaignon <paul.chaignon@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Negative test case for tail call map
Date: Fri, 4 Jul 2025 15:06:32 +0200 [thread overview]
Message-ID: <aGfR2NqZWL1c1-Mc@Tunnel> (raw)
In-Reply-To: <ad62770379cfcb7426a9a765bb59edb6d5d91fd1.camel@gmail.com>
On Thu, Jul 03, 2025 at 02:55:01PM -0700, Eduard Zingerman wrote:
> On Thu, 2025-07-03 at 23:36 +0200, Paul Chaignon wrote:
> > This patch adds a negative test case for the following verifier error.
> >
> > expected prog array map for tail call
> >
> > Signed-off-by: Paul Chaignon <paul.chaignon@gmail.com>
> > ---
>
> Nit: selftests/bpf/verifier binary is considered obsolete,
I didn't know that. Too bad, those verifier/ tests were easy to extract
and reuse as syzkaller seeds :)
I've sent a v2 with the new test format. Thanks for the review!
> new tests are mostly added as a part test_progs binary.
> E.g. you can add a file progs/verifier_tailcalls.c,
> register it in test_progs/verifier.c and define
> tests using test_loader framework, e.g. see
> progs/verifier_and.c.
>
> [...]
next prev parent reply other threads:[~2025-07-04 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 21:35 [PATCH bpf-next 1/2] bpf: Avoid warning on unexpected map for tail call Paul Chaignon
2025-07-03 21:36 ` [PATCH bpf-next 2/2] selftests/bpf: Negative test case for tail call map Paul Chaignon
2025-07-03 21:55 ` Eduard Zingerman
2025-07-04 13:06 ` Paul Chaignon [this message]
2025-07-03 21:51 ` [PATCH bpf-next 1/2] bpf: Avoid warning on unexpected map for tail call Eduard Zingerman
2025-07-04 2:40 ` 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=aGfR2NqZWL1c1-Mc@Tunnel \
--to=paul.chaignon@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@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