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 v8 8/9] bpf: Support private stack for struct_ops progs
Date: Thu, 31 Oct 2024 20:10:32 -0700 [thread overview]
Message-ID: <20241101031032.2680930-1-yonghong.song@linux.dev> (raw)
In-Reply-To: <20241101030950.2677215-1-yonghong.song@linux.dev>
For struct_ops progs, whether a particular prog will use private stack
or not (prog->aux->use_priv_stack) will be set before actual insn-level
verification for that prog. One particular implementation is to
piggyback on struct_ops->check_member(). The next patch will have an
example for this. The struct_ops->check_member() will set
prog->aux->use_priv_stack to be true which enables private stack
usage with ignoring BPF_PRIV_STACK_MIN_SIZE limit.
If use_priv_stack is true for a particular struct_ops prog, bpf
trampoline will need to do recursion checks (one level at this point)
to avoid stack overwrite. A field (recursion_skipped()) is added to
bpf_prog_aux structure such that if bpf_prog->aux->recursion_skipped
is set by the struct_ops subsystem, the function will be called
to terminate the prog run, collect related info, etc.
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
---
include/linux/bpf.h | 1 +
include/linux/bpf_verifier.h | 1 +
kernel/bpf/trampoline.c | 4 ++++
kernel/bpf/verifier.c | 36 ++++++++++++++++++++++++++++++++----
4 files changed, 38 insertions(+), 4 deletions(-)
diff --git a/include/linux/bpf.h b/include/linux/bpf.h
index 8a3ea7440a4a..7a34108c6974 100644
--- a/include/linux/bpf.h
+++ b/include/linux/bpf.h
@@ -1528,6 +1528,7 @@ struct bpf_prog_aux {
u64 prog_array_member_cnt; /* counts how many times as member of prog_array */
struct mutex ext_mutex; /* mutex for is_extended and prog_array_member_cnt */
struct bpf_arena *arena;
+ void (*recursion_skipped)(struct bpf_prog *prog); /* callback if recursion is skipped */
/* BTF_KIND_FUNC_PROTO for valid attach_btf_id */
const struct btf_type *attach_func_proto;
/* function name for valid attach_btf_id */
diff --git a/include/linux/bpf_verifier.h b/include/linux/bpf_verifier.h
index bc28ce7996ac..ff0fba935f89 100644
--- a/include/linux/bpf_verifier.h
+++ b/include/linux/bpf_verifier.h
@@ -889,6 +889,7 @@ static inline bool bpf_prog_check_recur(const struct bpf_prog *prog)
case BPF_PROG_TYPE_TRACING:
return prog->expected_attach_type != BPF_TRACE_ITER;
case BPF_PROG_TYPE_STRUCT_OPS:
+ return prog->aux->use_priv_stack;
case BPF_PROG_TYPE_LSM:
return false;
default:
diff --git a/kernel/bpf/trampoline.c b/kernel/bpf/trampoline.c
index 9f36c049f4c2..a84e60efbf89 100644
--- a/kernel/bpf/trampoline.c
+++ b/kernel/bpf/trampoline.c
@@ -899,6 +899,8 @@ static u64 notrace __bpf_prog_enter_recur(struct bpf_prog *prog, struct bpf_tram
if (unlikely(this_cpu_inc_return(*(prog->active)) != 1)) {
bpf_prog_inc_misses_counter(prog);
+ if (prog->aux->recursion_skipped)
+ prog->aux->recursion_skipped(prog);
return 0;
}
return bpf_prog_start_time();
@@ -975,6 +977,8 @@ u64 notrace __bpf_prog_enter_sleepable_recur(struct bpf_prog *prog,
if (unlikely(this_cpu_inc_return(*(prog->active)) != 1)) {
bpf_prog_inc_misses_counter(prog);
+ if (prog->aux->recursion_skipped)
+ prog->aux->recursion_skipped(prog);
return 0;
}
return bpf_prog_start_time();
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index 30e74db6a85f..865191c5d21b 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -6023,17 +6023,31 @@ static int check_ptr_alignment(struct bpf_verifier_env *env,
static int bpf_enable_priv_stack(struct bpf_verifier_env *env)
{
+ bool force_priv_stack = env->prog->aux->use_priv_stack;
struct bpf_subprog_info *si;
+ int ret;
+
+ if (!bpf_jit_supports_private_stack()) {
+ if (force_priv_stack) {
+ verbose(env, "Private stack not supported by jit\n");
+ return -EACCES;
+ }
- if (!bpf_jit_supports_private_stack())
return NO_PRIV_STACK;
+ }
+ ret = PRIV_STACK_ADAPTIVE;
switch (env->prog->type) {
case BPF_PROG_TYPE_KPROBE:
case BPF_PROG_TYPE_TRACEPOINT:
case BPF_PROG_TYPE_PERF_EVENT:
case BPF_PROG_TYPE_RAW_TRACEPOINT:
break;
+ case BPF_PROG_TYPE_STRUCT_OPS:
+ if (!force_priv_stack)
+ return NO_PRIV_STACK;
+ ret = PRIV_STACK_ALWAYS;
+ break;
case BPF_PROG_TYPE_TRACING:
if (env->prog->expected_attach_type != BPF_TRACE_ITER)
break;
@@ -6044,11 +6058,18 @@ static int bpf_enable_priv_stack(struct bpf_verifier_env *env)
si = env->subprog_info;
for (int i = 0; i < env->subprog_cnt; i++) {
- if (si[i].has_tail_call)
+ if (si[i].has_tail_call) {
+ if (ret == PRIV_STACK_ALWAYS) {
+ verbose(env,
+ "Private stack not supported due to tail call presence\n");
+ return -EACCES;
+ }
+
return NO_PRIV_STACK;
+ }
}
- return PRIV_STACK_ADAPTIVE;
+ return ret;
}
static int round_up_stack_depth(struct bpf_verifier_env *env, int stack_depth)
@@ -6121,7 +6142,8 @@ static int check_max_stack_depth_subprog(struct bpf_verifier_env *env, int idx,
idx, subprog_depth);
return -EACCES;
}
- if (subprog_depth >= BPF_PRIV_STACK_MIN_SIZE) {
+ if (priv_stack_supported == PRIV_STACK_ALWAYS ||
+ subprog_depth >= BPF_PRIV_STACK_MIN_SIZE) {
subprog[idx].use_priv_stack = true;
subprog_visited[idx] = 1;
}
@@ -6271,6 +6293,12 @@ static int check_max_stack_depth(struct bpf_verifier_env *env)
depth_frame, subtree_depth);
return -EACCES;
}
+ if (orig_priv_stack_supported == PRIV_STACK_ALWAYS) {
+ verbose(env,
+ "Private stack not supported due to possible nested subprog run\n");
+ ret = -EACCES;
+ goto out;
+ }
if (orig_priv_stack_supported == PRIV_STACK_ADAPTIVE) {
for (int i = 0; i < env->subprog_cnt; i++)
si[i].use_priv_stack = false;
--
2.43.5
next prev parent reply other threads:[~2024-11-01 3:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 3:09 [PATCH bpf-next v8 0/9] bpf: Support private stack for bpf progs Yonghong Song
2024-11-01 3:09 ` [PATCH bpf-next v8 1/9] bpf: Check stack depth limit after visiting all subprogs Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 2/9] bpf: Allow private stack to have each subprog having stack size of 512 bytes Yonghong Song
2024-11-01 19:46 ` Alexei Starovoitov
2024-11-04 0:05 ` Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 3/9] bpf: Check potential private stack recursion for progs with async callback Yonghong Song
2024-11-01 19:55 ` Alexei Starovoitov
2024-11-04 0:08 ` Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 4/9] bpf: Allocate private stack for eligible main prog or subprogs Yonghong Song
2024-11-01 20:18 ` Alexei Starovoitov
2024-11-04 0:10 ` Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 5/9] bpf, x86: Avoid repeated usage of bpf_prog->aux->stack_depth Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 6/9] bpf, x86: Support private stack in jit Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 7/9] selftests/bpf: Add tracing prog private stack tests Yonghong Song
2024-11-01 3:10 ` Yonghong Song [this message]
2024-11-01 20:13 ` [PATCH bpf-next v8 8/9] bpf: Support private stack for struct_ops progs Alexei Starovoitov
2024-11-04 0:35 ` Yonghong Song
2024-11-01 3:10 ` [PATCH bpf-next v8 9/9] selftests/bpf: Add struct_ops prog private stack tests 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=20241101031032.2680930-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