Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Mon, 14 Mar 2022 11:20:41 -0700 you wrote:
> Let's say that the caller has storage for num_elem stack frames. Then,
> the BPF stack helper functions walk the stack for only num_elem frames.
> This means that if skip > 0, one keeps only 'num_elem - skip' frames.
>
> This is because it sets init_nr in the perf_callchain_entry to the end
> of the buffer to save num_elem entries only. I believe it was because
> the perf callchain code unwound the stack frames until it reached the
> global max size (sysctl_perf_event_max_stack).
>
> [...]
Here is the summary with links:
- [v3,1/2] bpf: Adjust BPF stack helper functions to accommodate skip > 0
https://git.kernel.org/bpf/bpf-next/c/ee2a098851bf
- [v3,2/2] bpf/selftests: Test skipping stacktrace
https://git.kernel.org/bpf/bpf-next/c/e1cc1f39981b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
