diff options
| author | Masami Hiramatsu (Google) <mhiramat@kernel.org> | 2022-09-04 06:12:29 +0200 |
|---|---|---|
| committer | Steven Rostedt (Google) <rostedt@goodmis.org> | 2022-09-07 04:26:00 +0200 |
| commit | cecf8e128ec69149fe53c9a7bafa505a4bee25d9 (patch) | |
| tree | 99abc155af355e9e41bd14ec58905795756c4d2f /.gitattributes | |
| parent | tracing: hold caller_addr to hardirq_{enable,disable}_ip (diff) | |
| download | linux-cecf8e128ec69149fe53c9a7bafa505a4bee25d9.tar.xz linux-cecf8e128ec69149fe53c9a7bafa505a4bee25d9.zip | |
tracing: Fix to check event_mutex is held while accessing trigger list
Since the check_user_trigger() is called outside of RCU
read lock, this list_for_each_entry_rcu() caused a suspicious
RCU usage warning.
# echo hist:keys=pid > events/sched/sched_stat_runtime/trigger
# cat events/sched/sched_stat_runtime/trigger
[ 43.167032]
[ 43.167418] =============================
[ 43.167992] WARNING: suspicious RCU usage
[ 43.168567] 5.19.0-rc5-00029-g19ebe4651abf #59 Not tainted
[ 43.169283] -----------------------------
[ 43.169863] kernel/trace/trace_events_trigger.c:145 RCU-list traversed in non-reader section!!
...
However, this file->triggers list is safe when it is accessed
under event_mutex is held.
To fix this warning, adds a lockdep_is_held check to the
list_for_each_entry_rcu().
Link: https://lkml.kernel.org/r/166226474977.223837.1992182913048377113.stgit@devnote2
Cc: stable@vger.kernel.org
Fixes: 7491e2c44278 ("tracing: Add a probe that attaches to trace events")
Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions