From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 00/10] Teach libbpf to "fix up" BPF verifier log
Date: Mon, 25 Apr 2022 17:45:01 -0700 [thread overview]
Message-ID: <20220426004511.2691730-1-andrii@kernel.org> (raw)
This patch set teaches libbpf to enhance BPF verifier log with human-readable
and relevant information about failed CO-RE relocation. Patch #9 is the main
one with the new logic. See relevant commit messages for some more details.
All the other patches are either fixing various bugs detected
while working on this feature, most prominently a bug with libbpf not handling
CO-RE relocations for SEC("?...") programs, or are refactoring libbpf
internals to allow for easier reuse of CO-RE relo lookup and formatting logic.
Andrii Nakryiko (10):
libbpf: fix anonymous type check in CO-RE logic
libbpf: drop unhelpful "program too large" guess
libbpf: fix logic for finding matching program for CO-RE relocation
libbpf: avoid joining .BTF.ext data with BPF programs by section name
selftests/bpf: add CO-RE relos and SEC("?...") to linked_funcs
selftests
libbpf: record subprog-resolved CO-RE relocations unconditionally
libbpf: refactor CO-RE relo human description formatting routine
libbpf: simplify bpf_core_parse_spec() signature
libbpf: fix up verifier log for unguarded failed CO-RE relos
selftests/bpf: add libbpf's log fixup logic selftests
tools/lib/bpf/btf.c | 9 +-
tools/lib/bpf/libbpf.c | 252 ++++++++++++++----
tools/lib/bpf/libbpf_internal.h | 7 +
tools/lib/bpf/relo_core.c | 104 ++++----
tools/lib/bpf/relo_core.h | 6 +
.../selftests/bpf/prog_tests/linked_funcs.c | 6 +
.../selftests/bpf/prog_tests/log_fixup.c | 114 ++++++++
.../selftests/bpf/progs/linked_funcs1.c | 7 +-
.../selftests/bpf/progs/linked_funcs2.c | 7 +-
.../selftests/bpf/progs/test_log_fixup.c | 38 +++
tools/testing/selftests/bpf/test_progs.h | 11 +
11 files changed, 464 insertions(+), 97 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/log_fixup.c
create mode 100644 tools/testing/selftests/bpf/progs/test_log_fixup.c
--
2.30.2
next reply other threads:[~2022-04-26 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 0:45 Andrii Nakryiko [this message]
2022-04-26 0:45 ` [PATCH bpf-next 01/10] libbpf: fix anonymous type check in CO-RE logic Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 02/10] libbpf: drop unhelpful "program too large" guess Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 03/10] libbpf: fix logic for finding matching program for CO-RE relocation Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 04/10] libbpf: avoid joining .BTF.ext data with BPF programs by section name Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 05/10] selftests/bpf: add CO-RE relos and SEC("?...") to linked_funcs selftests Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 06/10] libbpf: record subprog-resolved CO-RE relocations unconditionally Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 07/10] libbpf: refactor CO-RE relo human description formatting routine Andrii Nakryiko
2022-04-26 18:52 ` Alexei Starovoitov
2022-04-26 22:20 ` Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 08/10] libbpf: simplify bpf_core_parse_spec() signature Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 09/10] libbpf: fix up verifier log for unguarded failed CO-RE relos Andrii Nakryiko
2022-04-26 18:59 ` Alexei Starovoitov
2022-04-26 22:16 ` Andrii Nakryiko
2022-04-26 0:45 ` [PATCH bpf-next 10/10] selftests/bpf: add libbpf's log fixup logic selftests Andrii Nakryiko
2022-04-26 22:50 ` [PATCH bpf-next 00/10] Teach libbpf to "fix up" BPF verifier log 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=20220426004511.2691730-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.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 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.