From: KP Singh <kpsingh@kernel.org>
To: bpf@vger.kernel.org
Cc: KP Singh <kpsingh@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Yosry Ahmed <yosryahmed@google.com>
Subject: [PATCH v4 bpf-next 3/5] bpf: Allow kfuncs to be used in LSM programs
Date: Fri, 24 Jun 2022 04:56:34 +0000 [thread overview]
Message-ID: <20220624045636.3668195-4-kpsingh@kernel.org> (raw)
In-Reply-To: <20220624045636.3668195-1-kpsingh@kernel.org>
In preparation for the addition of bpf_getxattr kfunc.
Signed-off-by: KP Singh <kpsingh@kernel.org>
---
kernel/bpf/btf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
index b31e8d8f2d4d..9f289b346790 100644
--- a/kernel/bpf/btf.c
+++ b/kernel/bpf/btf.c
@@ -7260,6 +7260,7 @@ static int bpf_prog_type_to_kfunc_hook(enum bpf_prog_type prog_type)
case BPF_PROG_TYPE_STRUCT_OPS:
return BTF_KFUNC_HOOK_STRUCT_OPS;
case BPF_PROG_TYPE_TRACING:
+ case BPF_PROG_TYPE_LSM:
return BTF_KFUNC_HOOK_TRACING;
case BPF_PROG_TYPE_SYSCALL:
return BTF_KFUNC_HOOK_SYSCALL;
--
2.37.0.rc0.104.g0611611a94-goog
next prev parent reply other threads:[~2022-06-24 4:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 4:56 [PATCH v4 bpf-next 0/5] Add bpf_getxattr KP Singh
2022-06-24 4:56 ` [PATCH v4 bpf-next 1/5] btf: Add a new kfunc set which allows to mark a function to be sleepable KP Singh
2022-06-24 4:56 ` [PATCH v4 bpf-next 2/5] bpf: kfunc support for ARG_PTR_TO_CONST_STR KP Singh
2022-06-24 22:03 ` Andrii Nakryiko
2022-06-25 1:26 ` KP Singh
2022-06-27 18:25 ` Andrii Nakryiko
2022-06-24 4:56 ` KP Singh [this message]
2022-06-24 4:56 ` [PATCH v4 bpf-next 4/5] bpf: Add a bpf_getxattr kfunc KP Singh
2022-06-24 4:56 ` [PATCH v4 bpf-next 5/5] bpf/selftests: Add a selftest for bpf_getxattr KP Singh
2022-06-24 21:57 ` Andrii Nakryiko
2022-06-27 7:04 ` [PATCH v4 bpf-next 0/5] Add bpf_getxattr Christoph Hellwig
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=20220624045636.3668195-4-kpsingh@kernel.org \
--to=kpsingh@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=yosryahmed@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox