From: patchwork-bot+netdevbpf@kernel.org
To: Arnaud Lecomte <contact@arnaud-lcm.com>
Cc: alexei.starovoitov@gmail.com, andrii.nakryiko@gmail.com,
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, song@kernel.org,
syzbot+c9b724fbb41cf2538b7b@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: Re: [PATCH V10 RESEND 1/2] bpf: refactor stack map trace depth calculation into helper function
Date: Tue, 28 Oct 2025 16:30:07 +0000 [thread overview]
Message-ID: <176166900751.2299764.16778692195336587842.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251025192858.31424-1-contact@arnaud-lcm.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 25 Oct 2025 19:28:58 +0000 you wrote:
> Extract the duplicated maximum allowed depth computation for stack
> traces stored in BPF stacks from bpf_get_stackid() and __bpf_get_stack()
> into a dedicated stack_map_calculate_max_depth() helper function.
>
> This unifies the logic for:
> - The max depth computation
> - Enforcing the sysctl_perf_event_max_stack limit
>
> [...]
Here is the summary with links:
- [V10,RESEND,1/2] bpf: refactor stack map trace depth calculation into helper function
https://git.kernel.org/bpf/bpf-next/c/e17d62fedd10
- [V10,RESEND,2/2] bpf: fix stackmap overflow check in __bpf_get_stackid()
https://git.kernel.org/bpf/bpf-next/c/23f852daa4ba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-28 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 19:28 [PATCH V10 RESEND 1/2] bpf: refactor stack map trace depth calculation into helper function Arnaud Lecomte
2025-10-25 19:29 ` [PATCH V10 RESEND 2/2] bpf: fix stackmap overflow check in __bpf_get_stackid() Arnaud Lecomte
2026-03-29 23:51 ` Guenter Roeck
2025-10-28 16:30 ` patchwork-bot+netdevbpf [this message]
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=176166900751.2299764.16778692195336587842.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@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=song@kernel.org \
--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