diff options
| author | Namhyung Kim <[email protected]> | 2024-11-26 19:13:31 -0800 |
|---|---|---|
| committer | Namhyung Kim <[email protected]> | 2024-12-02 12:36:20 -0800 |
| commit | 23c44f6c83257923b179461694edcf62749bedd5 (patch) | |
| tree | 8e0f3bb9f50acae48f0562c5828eee5d49b3995e /tools/testing/selftests/bpf/prog_tests/prog_array_init.c | |
| parent | 40384c840ea1944d7c5a392e8975ed088ecf0b37 (diff) | |
perf tools: Fix build-id event recording
The build-id events written at the end of the record session are broken
due to unexpected data. The write_buildid() writes the fixed length
event first and then variable length filename.
But a recent change made it write more data in the padding area
accidentally. So readers of the event see zero-filled data for the
next entry and treat it incorrectly. This resulted in wrong kernel
symbols because the kernel DSO loaded a random vmlinux image in the
path as it didn't have a valid build-id.
Fixes: ae39ba16554e ("perf inject: Fix build ID injection")
Reported-by: Linus Torvalds <[email protected]>
Tested-by: Arnaldo Carvalho de Melo <[email protected]>
Reviewed-by: Ian Rogers <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Namhyung Kim <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/prog_array_init.c')
0 files changed, 0 insertions, 0 deletions