diff options
| author |   Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com> | 2023-07-03 07:28:53 +0300 |
|---|---|---|
| committer |   Masami Hiramatsu (Google) <mhiramat@kernel.org> | 2023-07-11 00:44:57 +0900 |
| commit | cf0a624dc706c306294c14e6b3e7694702f25191 (patch) | |
| tree | a02574a4c77d36b656ab8ac11404a696897ab7ba /scripts/generate_rust_analyzer.py | |
| parent | fprobe: Release rethook after the ftrace_ops is unregistered (diff) | |
| download | linux-rng-cf0a624dc706c306294c14e6b3e7694702f25191.tar.xz linux-rng-cf0a624dc706c306294c14e6b3e7694702f25191.zip | |
kernel/trace: Fix cleanup logic of enable_trace_eprobe
The enable_trace_eprobe() function enables all event probes, attached
to given trace probe. If an error occurs in enabling one of the event
probes, all others should be roll backed. There is a bug in that roll
back logic - instead of all event probes, only the failed one is
disabled.
Link: https://lore.kernel.org/all/20230703042853.1427493-1-tz.stoyanov@gmail.com/
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Fixes: 7491e2c44278 ("tracing: Add a probe that attaches to trace events")
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions