From: Stanislav Fomichev <sdf@google.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v4 bpf-next 0/3] veristat: add better support of freplace programs
Date: Tue, 28 Mar 2023 10:25:16 -0700 [thread overview]
Message-ID: <ZCMi/IN1Z0VN1LdE@google.com> (raw)
In-Reply-To: <20230327185202.1929145-1-andrii@kernel.org>
On 03/27, Andrii Nakryiko wrote:
> Teach veristat how to deal with freplace BPF programs. As they can't be
> directly loaded by veristat without custom user-space part that sets
> correct
> target program FD, veristat always fails freplace programs. This patch set
> teaches veristat to guess target program type that will be inherited by
> freplace program itself, and subtitute it for BPF_PROG_TYPE_EXT
> (freplace) one
> for the purposes of BPF verification.
Acked-by: Stanislav Fomichev <sdf@google.com>
> Patch #1 fixes bug in libbpf preventing overriding freplace with specific
> program type.
> Patch #2 adds convenient -d flag to request veristat to emit libbpf debug
> logs. It help debugging why a specific BPF program fails to load, if the
> problem is not due to BPF verification itself.
> v3->v4:
> - fix optional kern_name check when guessing prog type (Alexei);
> v2->v3:
> - fix bpf_obj_id selftest that uses legacy bpf_prog_test_load() helper,
> which always sets program type programmatically; teach the helper to
> do it
> only if actually necessary (Stanislav);
> v1->v2:
> - fix compilation error reported by old GCC (my GCC v11 doesn't produce
> even
> a warning) and Clang (see CI failure at [0]):
> GCC version:
> veristat.c: In function ‘fixup_obj’:
> veristat.c:908:1: error: label at end of compound statement
> 908 | skip_freplace_fixup:
> | ^~~~~~~~~~~~~~~~~~~
> Clang version:
> veristat.c:909:1: error: label at end of compound statement is a C2x
> extension [-Werror,-Wc2x-extensions]
> }
> ^
> 1 error generated.
> [0]
> https://github.com/kernel-patches/bpf/actions/runs/4515972059/jobs/7953845335
> Andrii Nakryiko (3):
> libbpf: disassociate section handler on explicit
> bpf_program__set_type() call
> veristat: add -d debug mode option to see debug libbpf log
> veristat: guess and substitue underlying program type for freplace
> (EXT) progs
> tools/lib/bpf/libbpf.c | 1 +
> tools/testing/selftests/bpf/testing_helpers.c | 2 +-
> tools/testing/selftests/bpf/veristat.c | 129 +++++++++++++++++-
> 3 files changed, 126 insertions(+), 6 deletions(-)
> --
> 2.34.1
next prev parent reply other threads:[~2023-03-28 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 18:51 [PATCH v4 bpf-next 0/3] veristat: add better support of freplace programs Andrii Nakryiko
2023-03-27 18:52 ` [PATCH v4 bpf-next 1/3] libbpf: disassociate section handler on explicit bpf_program__set_type() call Andrii Nakryiko
2023-03-27 18:52 ` [PATCH v4 bpf-next 2/3] veristat: add -d debug mode option to see debug libbpf log Andrii Nakryiko
2023-03-29 17:37 ` Eduard Zingerman
2023-03-29 18:35 ` Andrii Nakryiko
2023-03-27 18:52 ` [PATCH v4 bpf-next 3/3] veristat: guess and substitue underlying program type for freplace (EXT) progs Andrii Nakryiko
2023-03-29 18:36 ` Eduard Zingerman
2023-03-30 5:38 ` Alexei Starovoitov
2023-03-30 14:48 ` Eduard Zingerman
2023-03-30 18:56 ` Andrii Nakryiko
2023-03-30 18:56 ` Andrii Nakryiko
2023-03-28 17:25 ` Stanislav Fomichev [this message]
2023-03-30 0:30 ` [PATCH v4 bpf-next 0/3] veristat: add better support of freplace programs 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=ZCMi/IN1Z0VN1LdE@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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