tracing: Have tracing_max_latency inc the trace array ref count
authorSteven Rostedt (Google) <rostedt@goodmis.org>
Thu, 7 Sep 2023 02:47:13 +0000 (22:47 -0400)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Thu, 7 Sep 2023 20:38:53 +0000 (16:38 -0400)
commit7d660c9b2bc95107f90a9f4c4759be85309a6550
tree7464736c2035613262ca7055990daa8384baf5d0
parentf5ca233e2e66dc1c249bf07eefa37e34a6c9346a
tracing: Have tracing_max_latency inc the trace array ref count

The tracing_max_latency file points to the trace_array max_latency field.
For an instance, if the file is opened and the instance is deleted,
reading or writing to the file will cause a use after free.

Up the ref count of the trace_array when tracing_max_latency is opened.

Link: https://lkml.kernel.org/r/20230907024803.666889383@goodmis.org
Link: https://lore.kernel.org/all/1cb3aee2-19af-c472-e265-05176fe9bd84@huawei.com/
Cc: stable@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Zheng Yejian <zhengyejian1@huawei.com>
Fixes: 8530dec63e7b4 ("tracing: Add tracing_check_open_get_tr()")
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
Tested-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace.c