summaryrefslogtreecommitdiffstats
tag nametrace-v5.19-rc5 (f64990a1b4d1e153bcb18e40634f008ce23cfbfd)
tag date2022-07-12 16:41:17 -0400
tagged bySteven Rostedt (Google) <rostedt@goodmis.org>
tagged objectcommit 1e1fb420fe...
downloadlinux-trace-trace-v5.19-rc5.tar.gz
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. -----BEGIN PGP SIGNATURE----- iIoEABYIADIWIQRRSw7ePDh/lE+zeZMp5XQQmuv6qgUCYs3fgBQccm9zdGVkdEBn b29kbWlzLm9yZwAKCRAp5XQQmuv6qlIKAQC9uvEb7fVduv834yU/HiPBbjYjZ7x5 q+G/6EbNVE5htwEA91IU90YdmCPDOkXovuUlTNB/1igvugFPQgR2BwIqgAQ= =+4E5 -----END PGP SIGNATURE-----