diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-06-18 10:24:50 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-06-18 10:24:50 -0700 |
commit | 5da3ff1fd0fdce7b5d9508c62403c04a8c96a1e5 (patch) | |
tree | 42d007aa169861eee80a46f3a0366786664c26e3 /rust/helpers/xarray.c | |
parent | 5a3b583f2050870e0403ffed650f06c94d7968a4 (diff) | |
parent | 327e28664307d49ce3fa71ba30dcc0007c270974 (diff) |
Merge tag 'ftrace-v6.16-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull ftrace fix from Steven Rostedt:
- Do not blindly enable function_graph tracer when updating
funcgraph-args
When the option to trace function arguments in the function graph
trace is updated, it requires the function graph tracer to switch its
callback routine. It disables function graph tracing, updates the
callback and then re-enables function graph tracing.
The issue is that it doesn't check if function graph tracing is
currently enabled or not. If it is not enabled, it will try to
disable it and re-enable it (which will actually enable it even
though it is not the current tracer). This causes an issue in the
accounting and will trigger a WARN_ON() if the function tracer is
enabled after that.
* tag 'ftrace-v6.16-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
fgraph: Do not enable function_graph tracer when setting funcgraph-args
Diffstat (limited to 'rust/helpers/xarray.c')
0 files changed, 0 insertions, 0 deletions