diff options
| author | Linus Torvalds <[email protected]> | 2022-07-12 16:17:40 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2022-07-12 16:17:40 -0700 |
| commit | b047602d579b4fb028128a525f056bbdc890e7f0 (patch) | |
| tree | e3dac342d77e53bb5681135b49a43ff100ef9cd0 /tools/testing/selftests/bpf/prog_tests/load_bytes_relative.c | |
| parent | 72a8e05d4f66b5af7854df4490e3135168694b6b (diff) | |
| parent | 1e1fb420fe68d9d938db360fec700dfd230cc22a (diff) | |
Merge tag 'trace-v5.19-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt:
"Fixes and minor clean ups for tracing:
- Fix memory leak by reverting what was thought to be a double free.
A static tool had gave a false positive that a double free was
possible in the error path, but it was actually a different
location that confused the static analyzer (and those of us that
reviewed it).
- Move use of static buffers by ftrace_dump() to a location that can
be used by kgdb's ftdump(), as it needs it for the same reasons.
- Clarify in the Kconfig description that function tracing has
negligible impact on x86, but may have a bit bigger impact on other
architectures.
- Remove unnecessary extra semicolon in trace event.
- Make a local variable static that is used in the fprobes sample
- Use KSYM_NAME_LEN for length of function in kprobe sample and get
rid of unneeded macro for the same purpose"
* tag 'trace-v5.19-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
samples: Use KSYM_NAME_LEN for kprobes
fprobe/samples: Make sample_probe static
blk-iocost: tracing: atomic64_read(&ioc->vtime_rate) is assigned an extra semicolon
ftrace: Be more specific about arch impact when function tracer is enabled
tracing: Fix sleeping while atomic in kdb ftdump
tracing/histograms: Fix memory leak problem
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/load_bytes_relative.c')
0 files changed, 0 insertions, 0 deletions