From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Sashiko <sashiko-bot@kernel.org>,
bpf@vger.kernel.org, Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
Quentin Monnet <qmo@kernel.org>, Tao Chen <chen.dylane@linux.dev>,
STAR Labs SG <info@starlabs.sg>,
Arnaud Lecomte <contact@arnaud-lcm.com>
Subject: Re: [PATCHv2 bpf-next 08/11] bpf: Restore trace->nr value properly in bpf_get_stack_pe
Date: Fri, 31 Jul 2026 15:33:42 +0200 [thread overview]
Message-ID: <amykNotpsnxhWNYI@krava> (raw)
In-Reply-To: <CAEf4BzZWgmL39Q8kQNu8B=-B1Vw2OipHvCaLbxCgU9XE6aNfVg@mail.gmail.com>
On Thu, Jul 30, 2026 at 04:01:28PM -0700, Andrii Nakryiko wrote:
> On Wed, Jul 29, 2026 at 1:39 AM Jiri Olsa <jolsa@kernel.org> wrote:
> >
> > In bpf_get_stack_pe The __bpf_get_stack call changes trace->nr value,
> > so both kernel and user path need to restore its value back.
> >
>
> something feels off here, this trace_in->nr restoration just in
> bpf_get_stack_pe is weird. maybe we should either make sure
> __bpf_get_stack doesn't modify trace_in->nr or restores it before
> returning to bpf_get_stack_pe()?..
I think it'd be cleaner not to modify the trace->nr and just
pass the wanted count as argument, will check
jirka
>
> > Reported-by: Sashiko <sashiko-bot@kernel.org>
> > Fixes: e17d62fedd10 ("bpf: Refactor stack map trace depth calculation into helper function")
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > kernel/bpf/stackmap.c | 14 ++++++--------
> > 1 file changed, 6 insertions(+), 8 deletions(-)
> >
> > diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
> > index 05269f2a9e08..875f530f3597 100644
> > --- a/kernel/bpf/stackmap.c
> > +++ b/kernel/bpf/stackmap.c
> > @@ -942,9 +942,9 @@ BPF_CALL_4(bpf_get_stack_pe, struct bpf_perf_event_data_kern *, ctx,
> > struct pt_regs *regs = (struct pt_regs *)(ctx->regs);
> > struct perf_event *event = ctx->event;
> > struct perf_callchain_entry *trace;
> > + __u64 nr, nr_kernel;
> > bool kernel, user;
> > int err = -EINVAL;
> > - __u64 nr_kernel;
> >
> > if (!(event->attr.sample_type & PERF_SAMPLE_CALLCHAIN))
> > return __bpf_get_stack(regs, NULL, NULL, buf, size, flags, false /* !may_fault */);
> > @@ -962,15 +962,12 @@ BPF_CALL_4(bpf_get_stack_pe, struct bpf_perf_event_data_kern *, ctx,
> > goto clear;
> >
> > nr_kernel = count_kernel_ip(trace);
> > + nr = trace->nr;
> >
> > if (kernel) {
> > - __u64 nr = trace->nr;
> > -
> > trace->nr = nr_kernel;
> > err = __bpf_get_stack(regs, NULL, trace, buf, size, flags, false /* !may_fault */);
> >
> > - /* restore nr */
> > - trace->nr = nr;
> > } else { /* user */
> > u64 skip = flags & BPF_F_SKIP_FIELD_MASK;
> >
> > @@ -981,12 +978,13 @@ BPF_CALL_4(bpf_get_stack_pe, struct bpf_perf_event_data_kern *, ctx,
> > flags = (flags & ~BPF_F_SKIP_FIELD_MASK) | skip;
> > err = __bpf_get_stack(regs, NULL, trace, buf, size, flags, false /* !may_fault */);
> > }
> > - return err;
> >
> > + /* restore nr */
> > + trace->nr = nr;
> > clear:
> > - memset(buf, 0, size);
> > + if (err < 0)
> > + memset(buf, 0, size);
> > return err;
> > -
> > }
> >
> > const struct bpf_func_proto bpf_get_stack_proto_pe = {
> > --
> > 2.54.0
> >
next prev parent reply other threads:[~2026-07-31 13:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:37 [PATCHv2 bpf-next 00/11] bpf: Disable preemption in stack map code Jiri Olsa
2026-07-29 8:37 ` [PATCHv2 bpf-next 01/11] bpf: Factor stackid_init function from __bpf_get_stackid Jiri Olsa
2026-07-29 8:51 ` sashiko-bot
2026-07-30 12:04 ` Jiri Olsa
2026-07-29 8:37 ` [PATCHv2 bpf-next 02/11] bpf: Factor stackid_fastpath " Jiri Olsa
2026-07-29 8:37 ` [PATCHv2 bpf-next 03/11] bpf: Factor stackid_new_bucket " Jiri Olsa
2026-07-29 8:38 ` [PATCHv2 bpf-next 04/11] bpf: Use stack id functions instead of __bpf_get_stackid Jiri Olsa
2026-07-29 9:42 ` bot+bpf-ci
2026-07-29 8:38 ` [PATCHv2 bpf-next 05/11] bpf: Disable preemption in bpf_get_stackid Jiri Olsa
2026-07-29 10:30 ` Leon Hwang
2026-07-30 11:38 ` Jiri Olsa
2026-07-30 13:43 ` Leon Hwang
2026-07-30 22:52 ` Andrii Nakryiko
2026-07-31 13:33 ` Jiri Olsa
2026-07-29 8:38 ` [PATCHv2 bpf-next 06/11] bpf: Factor callchain_store function from __bpf_get_stack Jiri Olsa
2026-07-29 8:57 ` sashiko-bot
2026-07-30 12:04 ` Jiri Olsa
2026-07-29 8:38 ` [PATCHv2 bpf-next 07/11] bpf: Factor callchain_finalize " Jiri Olsa
2026-07-29 9:41 ` bot+bpf-ci
2026-07-29 8:38 ` [PATCHv2 bpf-next 08/11] bpf: Restore trace->nr value properly in bpf_get_stack_pe Jiri Olsa
2026-07-30 23:01 ` Andrii Nakryiko
2026-07-31 13:33 ` Jiri Olsa [this message]
2026-07-29 8:38 ` [PATCHv2 bpf-next 09/11] bpf: Remove trace_in argument from __bpf_get_stack Jiri Olsa
2026-07-29 9:58 ` bot+bpf-ci
2026-07-30 23:06 ` Andrii Nakryiko
2026-07-31 13:33 ` Jiri Olsa
2026-07-31 15:14 ` Andrii Nakryiko
2026-08-03 7:37 ` Jiri Olsa
2026-08-03 17:45 ` Andrii Nakryiko
2026-07-29 8:38 ` [PATCHv2 bpf-next 10/11] bpf: Disable preemption in __bpf_get_stack Jiri Olsa
2026-07-29 8:38 ` [PATCHv2 bpf-next 11/11] bpf: Clear buf on error in __bpf_get_task_stack Jiri Olsa
2026-07-29 9:57 ` bot+bpf-ci
2026-07-30 12:04 ` Jiri Olsa
2026-07-30 23:11 ` Andrii Nakryiko
2026-07-31 13:33 ` Jiri Olsa
2026-07-31 15:18 ` Andrii Nakryiko
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=amykNotpsnxhWNYI@krava \
--to=olsajiri@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=contact@arnaud-lcm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=info@starlabs.sg \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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