diff options
| author | Eva Kurchatova <eva.kurchatova@virtuozzo.com> | 2026-09-25 16:35:41 +0300 |
|---|---|---|
| committer | Shuah Khan <skhan@linuxfoundation.org> | 2026-09-26 13:34:36 -0600 |
| commit | 30af56a227e27b892d34bc44c23298b5274913e3 (patch) | |
| tree | 874af55a2039b4d5c1ebdf600f1ec38d01c5e3d6 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 8459ea00c0abad92cbe4a9b836c4c979823dbb59 (diff) | |
| download | linux-next-30af56a227e27b892d34bc44c23298b5274913e3.tar.gz linux-next-30af56a227e27b892d34bc44c23298b5274913e3.zip | |
selftests/ftrace: skip gcov symbols when picking a function to probe
kprobe_eventname.tc takes the last kallsyms entry whose name ends in
vfs_read and puts a probe on it. On a kernel built with
CONFIG_GCOV_PROFILE_ALL=y the counter symbol gcc emits for the function
sorts after it:
ffffffff819bd1e0 T vfs_read
ffffffff845013e0 t __gcov_.vfs_read
so the test picks __gcov_.vfs_read, which is not a function entry, and
the write fails:
kprobe_eventname.tc: line 10: echo: write error: Invalid argument
Leave those symbols out of the choice. The test then picks vfs_read and
passes; without a coverage build nothing changes, as no such symbol
exists there.
This is the same class of problem as commit 23a4b108accc
("tracing/selftests: Fix kprobe event name test for .isra. functions"),
where a compiler-generated symbol was picked instead of a real function.
Link: https://lore.kernel.org/r/20260925133558.3636030-1-eva.kurchatova@virtuozzo.com
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
