bpf: Adjust BPF stack helper functions to accommodate skip > 0
authorNamhyung Kim <namhyung@kernel.org>
Mon, 14 Mar 2022 18:20:41 +0000 (11:20 -0700)
committerAlexei Starovoitov <ast@kernel.org>
Mon, 21 Mar 2022 02:16:23 +0000 (19:16 -0700)
commitee2a098851bfbe8bcdd964c0121f4246f00ff41e
treefb340d9c13b9ed24ef2b964a6c48149fab365467
parentef078600eec20f20eb7833cf597d4a5edf2953c1
bpf: Adjust BPF stack helper functions to accommodate skip > 0

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).

However it now has perf_callchain_entry_ctx.max_stack to limit the
iteration locally.  This simplifies the code to handle init_nr in the
BPF callstack entries and removes the confusion with the perf_event's
__PERF_SAMPLE_CALLCHAIN_EARLY which sets init_nr to 0.

Also change the comment on bpf_get_stack() in the header file to be
more explicit what the return value means.

Fixes: c195651e565a ("bpf: add bpf_get_stack helper")
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Yonghong Song <yhs@fb.com>
Link: https://lore.kernel.org/bpf/30a7b5d5-6726-1cc2-eaee-8da2828a9a9c@oracle.com
Link: https://lore.kernel.org/bpf/20220314182042.71025-1-namhyung@kernel.org
Based-on-patch-by: Eugene Loh <eugene.loh@oracle.com>
include/uapi/linux/bpf.h
kernel/bpf/stackmap.c