From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<martin.lau@kernel.org>
Cc: <andrii@kernel.org>, <kernel-team@meta.com>
Subject: [PATCH bpf-next 0/3] Verify global subprogs lazily
Date: Wed, 22 Nov 2023 13:31:09 -0800 [thread overview]
Message-ID: <20231122213112.3596548-1-andrii@kernel.org> (raw)
See patch #2 for justification. In few words, current eager verification of
global func prevents BPF CO-RE approaches to be applied to global functions.
Patch #1 is just a nicety to emit global subprog names in verifier logs.
Patch #3 adds selftests validating new lazy semantics.
Andrii Nakryiko (3):
bpf: emit global subprog name in verifier logs
bpf: validate global subprogs lazily
selftests/bpf: add lazy global subprog validation tests
include/linux/bpf.h | 2 +
kernel/bpf/verifier.c | 88 ++++++++++++++----
.../selftests/bpf/prog_tests/verifier.c | 2 +
.../selftests/bpf/progs/test_global_func12.c | 4 +-
.../bpf/progs/verifier_global_subprogs.c | 92 +++++++++++++++++++
.../bpf/progs/verifier_subprog_precision.c | 4 +-
6 files changed, 168 insertions(+), 24 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/verifier_global_subprogs.c
--
2.34.1
next reply other threads:[~2023-11-22 21:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 21:31 Andrii Nakryiko [this message]
2023-11-22 21:31 ` [PATCH bpf-next 1/3] bpf: emit global subprog name in verifier logs Andrii Nakryiko
2023-11-23 15:26 ` Eduard Zingerman
2023-11-22 21:31 ` [PATCH bpf-next 2/3] bpf: validate global subprogs lazily Andrii Nakryiko
2023-11-23 15:26 ` Eduard Zingerman
2023-11-22 21:31 ` [PATCH bpf-next 3/3] selftests/bpf: add lazy global subprog validation tests Andrii Nakryiko
2023-11-23 15:27 ` Eduard Zingerman
2023-11-23 22:48 ` [PATCH bpf-next 0/3] Verify global subprogs lazily Daniel Borkmann
2023-11-24 3:31 ` Andrii Nakryiko
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=20231122213112.3596548-1-andrii@kernel.org \
--to=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