tracing: Use ring_buffer_record_is_set_on() in tracer_tracing_is_on()
authorSven Schnelle <svens@linux.ibm.com>
Mon, 5 Feb 2024 06:53:40 +0000 (07:53 +0100)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Tue, 13 Feb 2024 17:04:17 +0000 (12:04 -0500)
commita6eaa24f1cc2c7aecec6047556bdfe32042094c3
tree76923262e62aae112de52af55b5226ba6a4bd0a9
parentbdbddb109c75365d22ec4826f480c5e75869e1cb
tracing: Use ring_buffer_record_is_set_on() in tracer_tracing_is_on()

tracer_tracing_is_on() checks whether record_disabled is not zero. This
checks both the record_disabled counter and the RB_BUFFER_OFF flag.
Reading the source it looks like this function should only check for
the RB_BUFFER_OFF flag. Therefore use ring_buffer_record_is_set_on().
This fixes spurious fails in the 'test for function traceon/off triggers'
test from the ftrace testsuite when the system is under load.

Link: https://lore.kernel.org/linux-trace-kernel/20240205065340.2848065-1-svens@linux.ibm.com
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tested-By: Mete Durlu <meted@linux.ibm.com>
Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace.c