From: Yonghong Song <yonghong.song@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: [PATCH bpf-next v5 4/9] bpf: Mark each subprog with proper private stack modes
Date: Thu, 17 Oct 2024 15:31:59 -0700 [thread overview]
Message-ID: <20241017223159.3176904-1-yonghong.song@linux.dev> (raw)
In-Reply-To: <20241017223138.3175885-1-yonghong.song@linux.dev>
Three private stack modes are used to direct jit action:
NO_PRIV_STACK: do not use private stack
PRIV_STACK_SUB_PROG: adjust frame pointer address (similar to normal stack)
PRIV_STACK_ROOT_PROG: set the frame pointer
Note that for subtree root prog (main prog or callback fn), even if the
bpf_prog stack size is 0, PRIV_STACK_ROOT_PROG mode is still used.
This is for bpf exception handling. More details can be found in
subsequent jit support and selftest patches.
Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
---
include/linux/bpf.h | 9 +++++++++
kernel/bpf/core.c | 19 +++++++++++++++++++
kernel/bpf/verifier.c | 29 +++++++++++++++++++++++++++++
3 files changed, 57 insertions(+)
diff --git a/include/linux/bpf.h b/include/linux/bpf.h
index a789cd2f5d6a..2c07a2e311f4 100644
--- a/include/linux/bpf.h
+++ b/include/linux/bpf.h
@@ -1457,6 +1457,12 @@ struct btf_mod_pair {
struct bpf_kfunc_desc_tab;
+enum bpf_priv_stack_mode {
+ NO_PRIV_STACK,
+ PRIV_STACK_SUB_PROG,
+ PRIV_STACK_ROOT_PROG,
+};
+
struct bpf_prog_aux {
atomic64_t refcnt;
u32 used_map_cnt;
@@ -1473,6 +1479,9 @@ struct bpf_prog_aux {
u32 ctx_arg_info_size;
u32 max_rdonly_access;
u32 max_rdwr_access;
+ enum bpf_priv_stack_mode priv_stack_mode;
+ u16 subtree_stack_depth; /* Subtree stack depth if PRIV_STACK_ROOT_PROG, 0 otherwise */
+ void __percpu *priv_stack_ptr;
struct btf *attach_btf;
const struct bpf_ctx_arg_aux *ctx_arg_info;
struct mutex dst_mutex; /* protects dst_* pointers below, *after* prog becomes visible */
diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
index 14d9288441f2..aee0055def4f 100644
--- a/kernel/bpf/core.c
+++ b/kernel/bpf/core.c
@@ -1240,6 +1240,7 @@ void __weak bpf_jit_free(struct bpf_prog *fp)
struct bpf_binary_header *hdr = bpf_jit_binary_hdr(fp);
bpf_jit_binary_free(hdr);
+ free_percpu(fp->aux->priv_stack_ptr);
WARN_ON_ONCE(!bpf_prog_kallsyms_verify_off(fp));
}
@@ -2421,6 +2422,24 @@ struct bpf_prog *bpf_prog_select_runtime(struct bpf_prog *fp, int *err)
if (*err)
return fp;
+ if (fp->aux->priv_stack_eligible) {
+ if (!fp->aux->stack_depth) {
+ fp->aux->priv_stack_mode = NO_PRIV_STACK;
+ } else {
+ void __percpu *priv_stack_ptr;
+
+ fp->aux->priv_stack_mode = PRIV_STACK_ROOT_PROG;
+ priv_stack_ptr =
+ __alloc_percpu_gfp(fp->aux->stack_depth, 8, GFP_KERNEL);
+ if (!priv_stack_ptr) {
+ *err = -ENOMEM;
+ return fp;
+ }
+ fp->aux->subtree_stack_depth = fp->aux->stack_depth;
+ fp->aux->priv_stack_ptr = priv_stack_ptr;
+ }
+ }
+
fp = bpf_int_jit_compile(fp);
bpf_prog_jit_attempt_done(fp);
if (!fp->jited && jit_needed) {
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index a14857015ad4..274b0b92177d 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -20010,6 +20010,8 @@ static int jit_subprogs(struct bpf_verifier_env *env)
{
struct bpf_prog *prog = env->prog, **func, *tmp;
int i, j, subprog_start, subprog_end = 0, len, subprog;
+ int subtree_top_idx, subtree_stack_depth;
+ void __percpu *priv_stack_ptr;
struct bpf_map *map_ptr;
struct bpf_insn *insn;
void *old_bpf_func;
@@ -20088,6 +20090,33 @@ static int jit_subprogs(struct bpf_verifier_env *env)
func[i]->is_func = 1;
func[i]->sleepable = prog->sleepable;
func[i]->aux->func_idx = i;
+
+ subtree_top_idx = env->subprog_info[i].subtree_top_idx;
+ if (env->subprog_info[subtree_top_idx].priv_stack_eligible) {
+ if (subtree_top_idx == i)
+ func[i]->aux->subtree_stack_depth =
+ env->subprog_info[i].subtree_stack_depth;
+
+ subtree_stack_depth = func[i]->aux->subtree_stack_depth;
+ if (subtree_top_idx != i) {
+ if (env->subprog_info[subtree_top_idx].subtree_stack_depth)
+ func[i]->aux->priv_stack_mode = PRIV_STACK_SUB_PROG;
+ else
+ func[i]->aux->priv_stack_mode = NO_PRIV_STACK;
+ } else if (!subtree_stack_depth) {
+ func[i]->aux->priv_stack_mode = PRIV_STACK_ROOT_PROG;
+ } else {
+ func[i]->aux->priv_stack_mode = PRIV_STACK_ROOT_PROG;
+ priv_stack_ptr =
+ __alloc_percpu_gfp(subtree_stack_depth, 8, GFP_KERNEL);
+ if (!priv_stack_ptr) {
+ err = -ENOMEM;
+ goto out_free;
+ }
+ func[i]->aux->priv_stack_ptr = priv_stack_ptr;
+ }
+ }
+
/* Below members will be freed only at prog->aux */
func[i]->aux->btf = prog->aux->btf;
func[i]->aux->func_info = prog->aux->func_info;
--
2.43.5
next prev parent reply other threads:[~2024-10-17 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 22:31 [PATCH bpf-next v5 0/9] bpf: Support private stack for bpf progs Yonghong Song
2024-10-17 22:31 ` [PATCH bpf-next v5 1/9] bpf: Allow each subprog having stack size of 512 bytes Yonghong Song
2024-10-17 22:31 ` [PATCH bpf-next v5 2/9] bpf: Support private stack for struct_ops programs Yonghong Song
2024-10-17 22:31 ` [PATCH bpf-next v5 3/9] sched-ext: Allow sched-ext progs to use private stack Yonghong Song
2024-10-17 22:31 ` Yonghong Song [this message]
2024-10-17 22:32 ` [PATCH bpf-next v5 5/9] bpf, x86: Refactor func emit_prologue Yonghong Song
2024-10-17 22:32 ` [PATCH bpf-next v5 6/9] bpf, x86: Create a helper for certain "reg <op>= imm" operations Yonghong Song
2024-10-17 22:32 ` [PATCH bpf-next v5 7/9] bpf, x86: Add jit support for private stack Yonghong Song
2024-10-20 19:52 ` kernel test robot
2024-10-21 4:44 ` Yonghong Song
2024-10-17 22:32 ` [PATCH bpf-next v5 8/9] selftests/bpf: Add tracing prog private stack tests Yonghong Song
2024-10-17 22:32 ` [PATCH bpf-next v5 9/9] selftests/bpf: Add struct_ops " Yonghong Song
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=20241017223159.3176904-1-yonghong.song@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=tj@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