From: Eduard Zingerman <eddyz87@gmail.com>
To: Paul Chaignon <paul.chaignon@gmail.com>, bpf@vger.kernel.org
Cc: 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: Thu, 03 Jul 2025 14:55:01 -0700 [thread overview]
Message-ID: <ad62770379cfcb7426a9a765bb59edb6d5d91fd1.camel@gmail.com> (raw)
In-Reply-To: <7cec754c8d4cc2d93a50e9091d7ccc7f33d454d4.1751578055.git.paul.chaignon@gmail.com>
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,
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-03 21:55 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 [this message]
2025-07-04 13:06 ` Paul Chaignon
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=ad62770379cfcb7426a9a765bb59edb6d5d91fd1.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=paul.chaignon@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