diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-01-03 19:04:43 +0100 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-01-03 19:04:43 +0100 |
commit | e30dd219c75023afc5f5ba76dbeb48e926cea645 (patch) | |
tree | 2fbae75c9758717d920fc4bf07b89f96138538aa /Documentation | |
parent | MAINTAINERS: Remove Olof from SoC maintainers (diff) | |
parent | ftrace: Fix function profiler's filtering functionality (diff) | |
download | linux-e30dd219c75023afc5f5ba76dbeb48e926cea645.tar.xz linux-e30dd219c75023afc5f5ba76dbeb48e926cea645.zip |
Merge tag 'ftrace-v6.13-rc5-2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull ftrace fixes from Steven Rostedt:
- Add needed READ_ONCE() around access to the fgraph array element
The updates to the fgraph array can happen when callbacks are
registered and unregistered. The __ftrace_return_to_handler() can
handle reading either the old value or the new value. But once it
reads that value it must stay consistent otherwise the check that
looks to see if the value is a stub may show false, but if the
compiler decides to re-read after that check, it can be true which
can cause the code to crash later on.
- Make function profiler use the top level ops for filtering again
When function graph became available for instances, its filter ops
became independent from the top level set_ftrace_filter. In the
process the function profiler received its own filter ops as well.
But the function profiler uses the top level set_ftrace_filter file
and does not have one of its own. In giving it its own filter ops, it
lost any user interface it once had. Make it use the top level
set_ftrace_filter file again. This fixes a regression.
* tag 'ftrace-v6.13-rc5-2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
ftrace: Fix function profiler's filtering functionality
fgraph: Add READ_ONCE() when accessing fgraph_array[]
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions