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,
Dave Marchevsky <davemarchevsky@meta.com>
Subject: [PATCH bpf-next 0/8] PTR_TO_BTF_ID arguments in global subprogs
Date: Thu, 4 Jan 2024 16:09:01 -0800 [thread overview]
Message-ID: <20240105000909.2818934-1-andrii@kernel.org> (raw)
This patch set follows recent changes that added btf_decl_tag-based argument
annotation support for global subprogs. This time we add ability to pass
PTR_TO_BTF_ID (BTF-aware kernel pointers) arguments into global subprograms.
We support explicitly trusted and untrusted arguments. Legacy semi-trusted
variant is not supported.
Patches #2 through #4 do preparatory refactorings to add support for multiple
tags per argument. This is important for being able to use modifiers like
__arg_nonnull together with trusted/untrusted arguments.
Patch #5 is adding the actual __arg_trusted and __arg_untrusted support.
It also raises a question about default nullable vs non-nullable semantics for
PTR_TO_BTF_ID arguments. It feels like having both __arg_nonnull and
__arg_nullable would provide the best kind of experience and flexibility, but
for now we implement nullable by default semantics, as a more conservative
behavior.
Patch #7 adds bpf_core_cast() helper macro which is a wrapper around
bpf_rdonly_cast() kfunc, but hides BTF ID manipulations behind more
user-friendly type argument instead. We utilize this macro in selftests added
in patch #8.
Patch #8 adds a bunch of positive and negative tests to validate expected
semantics for various trusted/untrusted + nullable/non-null variants. We also
make sure that global subprog cannot destroy PTR_TO_BTF_ID, as that would
wreak havoc in caller program that is not aware of this possibility.
There were proposals to do kernel-side type enforcement for __arg_ctx, let's
decide whether we should do that and for which program types, and I can
accommodate the logic in future revisions.
Cc: Dave Marchevsky <davemarchevsky@meta.com>
Andrii Nakryiko (8):
selftests/bpf: fix test_loader check message
bpf: make sure scalar args don't accept __arg_nonnull tag
bpf: prepare btf_prepare_func_args() for multiple tags per argument
bpf: support multiple tags per argument
bpf: add __arg_trusted and __arg_untrusted global func tags
libbpf: add __arg_trusted and __arg_untrusted annotation macros
libbpf: add bpf_core_cast() macro
selftests/bpf: add trusted/untrusted global subprog arg tests
include/linux/bpf.h | 2 +
include/linux/bpf_verifier.h | 1 +
kernel/bpf/btf.c | 228 +++++++++++++-----
kernel/bpf/verifier.c | 32 ++-
tools/lib/bpf/bpf_core_read.h | 13 +
tools/lib/bpf/bpf_helpers.h | 2 +
tools/testing/selftests/bpf/bpf_kfuncs.h | 2 +-
.../selftests/bpf/prog_tests/verifier.c | 2 +
.../bpf/progs/nested_trust_failure.c | 2 +-
.../bpf/progs/sk_storage_omem_uncharge.c | 2 -
tools/testing/selftests/bpf/progs/type_cast.c | 4 +-
.../bpf/progs/verifier_global_ptr_args.c | 160 ++++++++++++
tools/testing/selftests/bpf/test_loader.c | 2 +-
13 files changed, 387 insertions(+), 65 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/verifier_global_ptr_args.c
--
2.34.1
next reply other threads:[~2024-01-05 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 0:09 Andrii Nakryiko [this message]
2024-01-05 0:09 ` [PATCH bpf-next 1/8] selftests/bpf: fix test_loader check message Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 2/8] bpf: make sure scalar args don't accept __arg_nonnull tag Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 3/8] bpf: prepare btf_prepare_func_args() for multiple tags per argument Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 4/8] bpf: support " Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 5/8] bpf: add __arg_trusted and __arg_untrusted global func tags Andrii Nakryiko
2024-01-12 2:05 ` Alexei Starovoitov
2024-01-12 18:43 ` Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 6/8] libbpf: add __arg_trusted and __arg_untrusted annotation macros Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 7/8] libbpf: add bpf_core_cast() macro Andrii Nakryiko
2024-01-05 0:09 ` [PATCH bpf-next 8/8] selftests/bpf: add trusted/untrusted global subprog arg tests Andrii Nakryiko
2024-01-07 22:22 ` [PATCH bpf-next 0/8] PTR_TO_BTF_ID arguments in global subprogs Eduard Zingerman
2024-01-12 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=20240105000909.2818934-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@meta.com \
--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