From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
Stanislav Fomichev <sdf@google.com>
Subject: [PATCH bpf-next v5 6/8] libbpf: add lsm_cgoup_sock type
Date: Tue, 19 Apr 2022 12:00:51 -0700 [thread overview]
Message-ID: <20220419190053.3395240-7-sdf@google.com> (raw)
In-Reply-To: <20220419190053.3395240-1-sdf@google.com>
lsm_cgroup/ is the prefix for BPF_LSM_CGROUP.
Signed-off-by: Stanislav Fomichev <sdf@google.com>
---
tools/bpf/bpftool/common.c | 1 +
tools/lib/bpf/libbpf.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/tools/bpf/bpftool/common.c b/tools/bpf/bpftool/common.c
index c740142c24d8..a7a913784c47 100644
--- a/tools/bpf/bpftool/common.c
+++ b/tools/bpf/bpftool/common.c
@@ -66,6 +66,7 @@ const char * const attach_type_name[__MAX_BPF_ATTACH_TYPE] = {
[BPF_TRACE_FEXIT] = "fexit",
[BPF_MODIFY_RETURN] = "mod_ret",
[BPF_LSM_MAC] = "lsm_mac",
+ [BPF_LSM_CGROUP] = "lsm_cgroup",
[BPF_SK_LOOKUP] = "sk_lookup",
[BPF_TRACE_ITER] = "trace_iter",
[BPF_XDP_DEVMAP] = "xdp_devmap",
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index bf4f7ac54ebf..912cfa13814d 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -8701,6 +8701,7 @@ static const struct bpf_sec_def section_defs[] = {
SEC_DEF("freplace/", EXT, 0, SEC_ATTACH_BTF, attach_trace),
SEC_DEF("lsm/", LSM, BPF_LSM_MAC, SEC_ATTACH_BTF, attach_lsm),
SEC_DEF("lsm.s/", LSM, BPF_LSM_MAC, SEC_ATTACH_BTF | SEC_SLEEPABLE, attach_lsm),
+ SEC_DEF("lsm_cgroup/", LSM, BPF_LSM_CGROUP, SEC_ATTACH_BTF),
SEC_DEF("iter/", TRACING, BPF_TRACE_ITER, SEC_ATTACH_BTF, attach_iter),
SEC_DEF("iter.s/", TRACING, BPF_TRACE_ITER, SEC_ATTACH_BTF | SEC_SLEEPABLE, attach_iter),
SEC_DEF("syscall", SYSCALL, 0, SEC_SLEEPABLE),
@@ -9122,6 +9123,7 @@ void btf_get_kernel_prefix_kind(enum bpf_attach_type attach_type,
*kind = BTF_KIND_TYPEDEF;
break;
case BPF_LSM_MAC:
+ case BPF_LSM_CGROUP:
*prefix = BTF_LSM_PREFIX;
*kind = BTF_KIND_FUNC;
break;
--
2.36.0.rc0.470.gd361397f0d-goog
next prev parent reply other threads:[~2022-04-19 19:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 19:00 [PATCH bpf-next v5 0/8] bpf: cgroup_sock lsm flavor Stanislav Fomichev
2022-04-19 19:00 ` [PATCH bpf-next v5 1/8] bpf: add bpf_func_t and trampoline helpers Stanislav Fomichev
2022-04-19 19:00 ` [PATCH bpf-next v5 2/8] bpf: convert cgroup_bpf.progs to hlist Stanislav Fomichev
2022-04-19 19:00 ` [PATCH bpf-next v5 3/8] bpf: per-cgroup lsm flavor Stanislav Fomichev
2022-04-26 6:27 ` Martin KaFai Lau
2022-04-26 6:30 ` Martin KaFai Lau
2022-04-26 22:44 ` Stanislav Fomichev
2022-04-27 0:10 ` Martin KaFai Lau
2022-04-27 17:47 ` Stanislav Fomichev
2022-04-27 20:17 ` Martin KaFai Lau
2022-04-19 19:00 ` [PATCH bpf-next v5 4/8] bpf: minimize number of allocated lsm slots per program Stanislav Fomichev
2022-04-19 19:00 ` [PATCH bpf-next v5 5/8] bpf: allow writing to a subset of sock fields from lsm progtype Stanislav Fomichev
2022-04-19 19:00 ` Stanislav Fomichev [this message]
2022-04-19 19:00 ` [PATCH bpf-next v5 7/8] selftests/bpf: lsm_cgroup functional test Stanislav Fomichev
2022-04-19 19:00 ` [PATCH bpf-next v5 8/8] selftests/bpf: verify lsm_cgroup struct sock access Stanislav Fomichev
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=20220419190053.3395240-7-sdf@google.com \
--to=sdf@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.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