summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorKumar Kartikeya Dwivedi <memxor@gmail.com>2026-07-12 01:55:52 +0200
committerKumar Kartikeya Dwivedi <memxor@gmail.com>2026-07-12 01:56:22 +0200
commit9a3a07d06e7d74f4aecc51396c771149336ac55d (patch)
tree430e86e888cb7c590db3003352387ed9a27ecf58 /tools/perf/scripts/python/stackcollapse.py
parent25935519f78be63048f4a964e15be48c83ba7dc2 (diff)
parent539d3edf8e53f10b2d63e2d866e23c414c99e921 (diff)
Merge branch 'bpf-fix-warning-in-bpf_trampoline_multi_detach'
Leon Hwang says: ==================== bpf: Fix WARNING in bpf_trampoline_multi_detach Since tracing_multi link does not set ftrace_managed, it would fail to release the tracing_multi link when attaching tracing_multi link and then attaching fentry link. [ 3.714215] WARNING: kernel/bpf/trampoline.c:1727 at bpf_trampoline_multi_detach+0x20b/0x240, CPU#1: test_progs/97 ... [ 3.733170] bpf_tracing_multi_link_release+0x14/0x30 [ 3.733890] bpf_link_free+0x58/0x130 [ 3.734414] bpf_link_release+0x23/0x30 Fix it by setting 'ftrace_managed = true' in register_fentry_multi(). Note: the reason of targeting bpf-next tree is I'm planning to add tracing_multi link support for bpf progs, that would rely on the fix and have code conflict with the test. Changes: v1 -> v2: * Collect Acked-by from Jiri, thanks. * Check arg using tracing_multi_arg_check() in bpf prog in test. (per Sashiko) * v1: https://lore.kernel.org/bpf/20260710144734.78203-1-leon.hwang@linux.dev/ ==================== Link: https://patch.msgid.link/20260711124822.29406-1-leon.hwang@linux.dev Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions