rcu: Define tracepoint strings only if CONFIG_TRACING is set
Commit f7f7bac9 ("rcu: Have the RCU tracepoints use the tracepoint_string infrastructure") unconditionally populates the __tracepoint_str input section, but this section is not assigned an output section if CONFIG_TRACING is not set. This results in the __tracepoint_str turning up in unexpected places, i.e., after _edata. Signed-off-by:Ard Biesheuvel <ard.biesheuvel@linaro.org> Reviewed-by:
Steven Rostedt <rostedt@goodmis.org> Signed-off-by:
Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Showing
Please register or sign in to comment