From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: Alexei Starovoitov <alexei.starovoitov@gmail•com>, davem@davemloft•net
Cc: daniel@iogearbox•net, andrii@kernel•org, martin.lau@kernel•org,
void@manifault•com, davemarchevsky@meta•com, tj@kernel•org,
memxor@gmail•com, netdev@vger•kernel.org, bpf@vger•kernel.org,
kernel-team@fb•com
Subject: Re: [PATCH bpf-next 0/2] bpf: Add detection of kfuncs.
Date: Thu, 16 Mar 2023 11:31:08 +0100 [thread overview]
Message-ID: <87jzzh9edv.fsf@toke.dk> (raw)
In-Reply-To: <20230315223607.50803-1-alexei.starovoitov@gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail•com> writes:
> From: Alexei Starovoitov <ast@kernel•org>
>
> Allow BPF programs detect at load time whether particular kfunc exists.
>
> Alexei Starovoitov (2):
> bpf: Allow ld_imm64 instruction to point to kfunc.
> selftests/bpf: Add test for bpf_kfunc_exists().
>
> kernel/bpf/verifier.c | 7 +++++--
> tools/lib/bpf/bpf_helpers.h | 3 +++
> .../selftests/bpf/progs/task_kfunc_success.c | 14 +++++++++++++-
> 3 files changed, 21 insertions(+), 3 deletions(-)
Nice!
For the series:
Reviewed-by: Toke Høiland-Jørgensen <toke@redhat•com>
prev parent reply other threads:[~2023-03-16 10:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 22:36 [PATCH bpf-next 0/2] bpf: Add detection of kfuncs Alexei Starovoitov
2023-03-15 22:36 ` [PATCH bpf-next 1/2] bpf: Allow ld_imm64 instruction to point to kfunc Alexei Starovoitov
2023-03-16 14:14 ` Eduard Zingerman
2023-03-16 16:45 ` Alexei Starovoitov
2023-03-16 20:34 ` Andrii Nakryiko
2023-03-16 22:25 ` Alexei Starovoitov
2023-03-16 23:06 ` Andrii Nakryiko
2023-03-17 1:39 ` Alexei Starovoitov
2023-03-17 16:28 ` Andrii Nakryiko
2023-03-15 22:36 ` [PATCH bpf-next 2/2] selftests/bpf: Add test for bpf_kfunc_exists() Alexei Starovoitov
2023-03-16 20:34 ` Andrii Nakryiko
2023-03-16 22:35 ` Alexei Starovoitov
2023-03-16 23:23 ` Andrii Nakryiko
2023-03-16 0:33 ` [PATCH bpf-next 0/2] bpf: Add detection of kfuncs Martin KaFai Lau
2023-03-16 5:34 ` John Fastabend
2023-03-16 10:31 ` Toke Høiland-Jørgensen [this message]
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=87jzzh9edv.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=andrii@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=davemarchevsky@meta$(echo .)com \
--cc=kernel-team@fb$(echo .)com \
--cc=martin.lau@kernel$(echo .)org \
--cc=memxor@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
--cc=void@manifault$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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