From: Tao Chen <chen.dylane@linux.dev>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, song@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 2/2] bpf: Use per-cpu BPF callchain entry to save callchain
Date: Mon, 20 Oct 2025 13:50:50 +0800 [thread overview]
Message-ID: <4c35feba-e075-42c1-82c5-5589c16f088e@linux.dev> (raw)
In-Reply-To: <20251019170118.2955346-3-chen.dylane@linux.dev>
在 2025/10/20 01:01, Tao Chen 写道:
> As Alexei noted, get_perf_callchain() return values may be reused
> if a task is preempted after the BPF program enters migrate disable
> mode. Drawing on the per-cpu design of bpf_bprintf_buffers,
> per-cpu BPF callchain entry is used here.
>
> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
> ---
> kernel/bpf/stackmap.c | 98 ++++++++++++++++++++++++++++++++-----------
> 1 file changed, 74 insertions(+), 24 deletions(-)
>
> diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
> index 94e46b7f340..3513077c57d 100644
> --- a/kernel/bpf/stackmap.c
> +++ b/kernel/bpf/stackmap.c
> @@ -31,6 +31,52 @@ struct bpf_stack_map {
> struct stack_map_bucket *buckets[] __counted_by(n_buckets);
> };
>
> +struct bpf_perf_callchain_entry {
> + u64 nr;
> + u64 ip[PERF_MAX_STACK_DEPTH];
> +};
> +
> +#define MAX_PERF_CALLCHAIN_PREEMPT 3
> +static DEFINE_PER_CPU(struct bpf_perf_callchain_entry[MAX_PERF_CALLCHAIN_PREEMPT],
> + bpf_perf_callchain_entries);
> +static DEFINE_PER_CPU(int, bpf_perf_callchain_preempt_cnt);
> +
> +static int bpf_get_perf_callchain_or_entry(struct perf_callchain_entry **entry,
> + struct pt_regs *regs, bool kernel,
> + bool user, u32 max_stack, bool crosstack,
> + bool add_mark, bool get_callchain)
> +{
> + struct bpf_perf_callchain_entry *bpf_entry;
> + struct perf_callchain_entry *perf_entry;
> + int preempt_cnt;
> +
> + preempt_cnt = this_cpu_inc_return(bpf_perf_callchain_preempt_cnt);
> + if (WARN_ON_ONCE(preempt_cnt > MAX_PERF_CALLCHAIN_PREEMPT)) {
> + this_cpu_dec(bpf_perf_callchain_preempt_cnt);
> + return -EBUSY;
> + }
> +
> + bpf_entry = this_cpu_ptr(&bpf_perf_callchain_entries[preempt_cnt - 1]);
> + if (!get_callchain) {
> + *entry = (struct perf_callchain_entry *)bpf_entry;
> + return 0;
> + }
> +
> + perf_entry = get_perf_callchain(regs, (struct perf_callchain_entry *)bpf_entry,
> + kernel, user, max_stack,
> + crosstack, add_mark);
> + *entry = perf_entry;
> +
> + return 0;
> +}
> +
> +static void bpf_put_perf_callchain(void)
> +{
> + if (WARN_ON_ONCE(this_cpu_read(bpf_perf_callchain_preempt_cnt) == 0))
> + return;
> + this_cpu_dec(bpf_perf_callchain_preempt_cnt);
> +}
> +
> static inline bool stack_map_use_build_id(struct bpf_map *map)
> {
> return (map->map_flags & BPF_F_STACK_BUILD_ID);
> @@ -192,11 +238,11 @@ get_callchain_entry_for_task(struct task_struct *task, u32 max_depth)
> {
> #ifdef CONFIG_STACKTRACE
> struct perf_callchain_entry *entry;
> - int rctx;
> -
> - entry = get_callchain_entry(&rctx);
> + int ret;
>
> - if (!entry)
> + ret = bpf_get_perf_callchain_or_entry(&entry, NULL, false, false, 0, false, false,
> + false);
> + if (ret)
> return NULL;
>
> entry->nr = stack_trace_save_tsk(task, (unsigned long *)entry->ip,
> @@ -216,7 +262,7 @@ get_callchain_entry_for_task(struct task_struct *task, u32 max_depth)
> to[i] = (u64)(from[i]);
> }
>
> - put_callchain_entry(rctx);
> + bpf_put_perf_callchain();
double-put issue here reported by AI, i will fix it.
>
> return entry;
> #else /* CONFIG_STACKTRACE */
> @@ -305,6 +351,7 @@ BPF_CALL_3(bpf_get_stackid, struct pt_regs *, regs, struct bpf_map *, map,
> bool user = flags & BPF_F_USER_STACK;
> struct perf_callchain_entry *trace;
> bool kernel = !user;
> + int err;
>
> if (unlikely(flags & ~(BPF_F_SKIP_FIELD_MASK | BPF_F_USER_STACK |
> BPF_F_FAST_STACK_CMP | BPF_F_REUSE_STACKID)))
> @@ -314,14 +361,15 @@ BPF_CALL_3(bpf_get_stackid, struct pt_regs *, regs, struct bpf_map *, map,
> if (max_depth > sysctl_perf_event_max_stack)
> max_depth = sysctl_perf_event_max_stack;
>
> - trace = get_perf_callchain(regs, NULL, kernel, user, max_depth,
> - false, false);
> + err = bpf_get_perf_callchain_or_entry(&trace, regs, kernel, user, max_depth,
> + false, false, true);
> + if (err)
> + return err;
>
> - if (unlikely(!trace))
> - /* couldn't fetch the stack trace */
> - return -EFAULT;
> + err = __bpf_get_stackid(map, trace, flags);
> + bpf_put_perf_callchain();
>
> - return __bpf_get_stackid(map, trace, flags);
> + return err;
> }
>
> const struct bpf_func_proto bpf_get_stackid_proto = {
> @@ -443,20 +491,23 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
> if (sysctl_perf_event_max_stack < max_depth)
> max_depth = sysctl_perf_event_max_stack;
>
> - if (may_fault)
> - rcu_read_lock(); /* need RCU for perf's callchain below */
> -
> if (trace_in)
> trace = trace_in;
> - else if (kernel && task)
> + else if (kernel && task) {
> trace = get_callchain_entry_for_task(task, max_depth);
> - else
> - trace = get_perf_callchain(regs, NULL, kernel, user, max_depth,
> - crosstask, false);
> + } else {
> + err = bpf_get_perf_callchain_or_entry(&trace, regs, kernel, user, max_depth,
> + false, false, true);
> + if (err)
> + return err;
> + }
> +
> + if (unlikely(!trace))
> + goto err_fault;
>
> - if (unlikely(!trace) || trace->nr < skip) {
> - if (may_fault)
> - rcu_read_unlock();
> + if (trace->nr < skip) {
> + if (!trace_in)
> + bpf_put_perf_callchain();
> goto err_fault;
> }
>
> @@ -475,9 +526,8 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
> memcpy(buf, ips, copy_len);
> }
>
> - /* trace/ips should not be dereferenced after this point */
> - if (may_fault)
> - rcu_read_unlock();
> + if (!trace_in)
> + bpf_put_perf_callchain();
>
> if (user_build_id)
> stack_map_get_build_id_offset(buf, trace_nr, user, may_fault);
--
Best Regards
Tao Chen
next prev parent reply other threads:[~2025-10-20 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 17:01 [RFC PATCH bpf-next v3 0/2] Pass external callchain entry to get_perf_callchain Tao Chen
2025-10-19 17:01 ` [PATCH bpf-next v3 1/2] perf: Use extern perf_callchain_entry for get_perf_callchain Tao Chen
2025-10-20 11:40 ` Peter Zijlstra
2025-10-22 15:14 ` Tao Chen
2025-10-19 17:01 ` [PATCH bpf-next v3 2/2] bpf: Use per-cpu BPF callchain entry to save callchain Tao Chen
2025-10-20 5:50 ` Tao Chen [this message]
2025-10-20 11:03 ` Peter Zijlstra
2025-10-22 15:59 ` Tao Chen
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=4c35feba-e075-42c1-82c5-5589c16f088e@linux.dev \
--to=chen.dylane@linux.dev \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).