From: Song Liu <song@kernel.org>
To: Arnaud Lecomte <contact@arnaud-lcm.com>,
alexei.starovoitov@gmail.com, yonghong.song@linux.dev
Cc: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@fomichev.me,
syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH bpf-next v7 2/3] bpf: clean-up bounds checking in __bpf_get_stack
Date: Thu, 4 Sep 2025 15:40:43 -0700 [thread overview]
Message-ID: <05b2c226-9a09-4541-a18c-8a21898846d0@kernel.org> (raw)
In-Reply-To: <20250903234052.29678-1-contact@arnaud-lcm.com>
On 9/3/25 4:40 PM, Arnaud Lecomte wrote:
> Clean-up bounds checking for trace->nr in
> __bpf_get_stack by limiting it only to
> max_depth.
>
> Signed-off-by: Arnaud Lecomte <contact@arnaud-lcm.com>
> Cc: Song Lui <song@kernel.org>
Typo in my name, which is "Song Liu".
This looks right.
Acked-by: Song Liu <song@kernel.org>
> ---
> kernel/bpf/stackmap.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
> index ed707bc07173..9f3ae426ddc3 100644
> --- a/kernel/bpf/stackmap.c
> +++ b/kernel/bpf/stackmap.c
> @@ -462,13 +462,15 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
> if (may_fault)
> rcu_read_lock(); /* need RCU for perf's callchain below */
>
> - if (trace_in)
> + if (trace_in) {
> trace = trace_in;
> - else if (kernel && task)
> + trace->nr = min_t(u32, trace->nr, max_depth);
> + } else if (kernel && task) {
> trace = get_callchain_entry_for_task(task, max_depth);
> - else
> + } else {
> trace = get_perf_callchain(regs, 0, kernel, user, max_depth,
> crosstask, false);
> + }
>
> if (unlikely(!trace) || trace->nr < skip) {
> if (may_fault)
> @@ -477,7 +479,6 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
> }
>
> trace_nr = trace->nr - skip;
> - trace_nr = (trace_nr <= num_elem) ? trace_nr : num_elem;
> copy_len = trace_nr * elem_size;
>
> ips = trace->ip + skip;
next prev parent reply other threads:[~2025-09-04 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 23:39 [PATCH bpf-next v7 1/3] bpf: refactor max_depth computation in bpf_get_stack() Arnaud Lecomte
2025-09-03 23:40 ` [PATCH bpf-next v7 2/3] bpf: clean-up bounds checking in __bpf_get_stack Arnaud Lecomte
2025-09-03 23:43 ` [PATCH bpf-next v7 3/3] bpf: fix stackmap overflow check in __bpf_get_stackid() Arnaud Lecomte
2025-09-04 22:45 ` Song Liu
2025-09-04 22:53 ` Lecomte, Arnaud
2025-09-04 22:40 ` Song Liu [this message]
2025-09-04 22:52 ` [PATCH bpf-next v7 2/3] bpf: clean-up bounds checking in __bpf_get_stack Lecomte, Arnaud
2025-09-04 22:41 ` [PATCH bpf-next v7 1/3] bpf: refactor max_depth computation in bpf_get_stack() Song Liu
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=05b2c226-9a09-4541-a18c-8a21898846d0@kernel.org \
--to=song@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=contact@arnaud-lcm.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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