From: thinker.li@gmail.com
To: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
drosen@google.com
Cc: sinquersw@gmail.com, kuifeng@meta.com,
Kui-Feng Lee <thinker.li@gmail.com>
Subject: [PATCH bpf-next v4 8/9] bpf: export btf_ctx_access to modules.
Date: Fri, 13 Oct 2023 15:43:03 -0700 [thread overview]
Message-ID: <20231013224304.187218-9-thinker.li@gmail.com> (raw)
In-Reply-To: <20231013224304.187218-1-thinker.li@gmail.com>
From: Kui-Feng Lee <thinker.li@gmail.com>
The module requires the use of btf_ctx_access() to invoke
bpf_tracing_btf_ctx_access() from a module. This function is valuable for
implementing validation functions that ensure proper access to ctx.
Signed-off-by: Kui-Feng Lee <thinker.li@gmail.com>
---
kernel/bpf/btf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
index 990973d6057d..dc6d8fe9b63d 100644
--- a/kernel/bpf/btf.c
+++ b/kernel/bpf/btf.c
@@ -6141,6 +6141,7 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
__btf_name_by_offset(btf, t->name_off));
return true;
}
+EXPORT_SYMBOL_GPL(btf_ctx_access);
enum bpf_struct_walk_result {
/* < 0 error */
--
2.34.1
next prev parent reply other threads:[~2023-10-13 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 22:42 [PATCH bpf-next v4 0/9] Registrating struct_ops types from modules thinker.li
2023-10-13 22:42 ` [PATCH bpf-next v4 1/9] bpf: refactory struct_ops type initialization to a function thinker.li
2023-10-13 22:42 ` [PATCH bpf-next v4 2/9] bpf: add struct_ops_tab to btf thinker.li
2023-10-13 22:42 ` [PATCH bpf-next v4 3/9] bpf: hold module for bpf_struct_ops_map thinker.li
2023-10-13 22:42 ` [PATCH bpf-next v4 4/9] bpf: validate value_type thinker.li
2023-10-13 22:43 ` [PATCH bpf-next v4 5/9] bpf: pass attached BTF to the bpf_struct_ops subsystem thinker.li
2023-10-13 22:43 ` [PATCH bpf-next v4 6/9] bpf, net: switch to dynamic registration thinker.li
2023-10-13 22:43 ` [PATCH bpf-next v4 7/9] libbpf: Find correct module BTFs for struct_ops maps and progs thinker.li
2023-10-13 22:43 ` thinker.li [this message]
2023-10-13 22:43 ` [PATCH bpf-next v4 9/9] selftests/bpf: test case for register_bpf_struct_ops() thinker.li
2023-10-17 16:29 ` [PATCH bpf-next v4 0/9] Registrating struct_ops types from modules Kui-Feng Lee
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=20231013224304.187218-9-thinker.li@gmail.com \
--to=thinker.li@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=drosen@google.com \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sinquersw@gmail.com \
--cc=song@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.