mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Linux trace kernel" <linux-trace-kernel@vger.kernel.org>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"\"Fusheng Huang( 黄富生) \"" <Fusheng.Huang@luxshare-ict.com>
Subject: Re: [PATCH v2] tracing: Add down_write(trace_event_sem) when adding trace event
Date: Sat, 19 Jul 2025 13:36:34 +0900	[thread overview]
Message-ID: <20250719133634.f424cba37241e73b0f774a7f@kernel.org> (raw)
In-Reply-To: <20250718223158.799bfc0c@batman.local.home>

On Fri, 18 Jul 2025 22:31:58 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> From: Steven Rostedt <rostedt@goodmis.org>
> 
> When a module is loaded, it adds trace events defined by the module. It
> may also need to modify the modules trace printk formats to replace enum
> names with their values.
> 
> If two modules are loaded at the same time, the adding of the event to the
> ftrace_events list can corrupt the walking of the list in the code that is
> modifying the printk format strings and crash the kernel.
> 
> The addition of the event should take the trace_event_sem for write while
> it adds the new event.
> 
> Also add a lockdep_assert_held() on that semaphore in
> __trace_add_event_dirs() as it iterates the list.

Looks good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

Thanks!

> 
> Cc: stable@vger.kernel.org
> Reported-by: Fusheng Huang(黄富生)  <Fusheng.Huang@luxshare-ict.com>
> Closes: https://lore.kernel.org/all/20250717105007.46ccd18f@batman.local.home/
> Fixes: 110bf2b764eb6 ("tracing: add protection around module events unload")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> Changes since v1: https://lore.kernel.org/20250717131204.74559b88@batman.local.home
> 
> - Replace lockdep_assert_held_read() with lockdep_assert_held() as it is
>   actually held with down_write() when it is called.
> 
>  kernel/trace/trace_events.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 120531268abf..d01e5c910ce1 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -3136,7 +3136,10 @@ __register_event(struct trace_event_call *call, struct module *mod)
>  	if (ret < 0)
>  		return ret;
>  
> +	down_write(&trace_event_sem);
>  	list_add(&call->list, &ftrace_events);
> +	up_write(&trace_event_sem);
> +
>  	if (call->flags & TRACE_EVENT_FL_DYNAMIC)
>  		atomic_set(&call->refcnt, 0);
>  	else
> @@ -3750,6 +3753,8 @@ __trace_add_event_dirs(struct trace_array *tr)
>  	struct trace_event_call *call;
>  	int ret;
>  
> +	lockdep_assert_held(&trace_event_sem);
> +
>  	list_for_each_entry(call, &ftrace_events, list) {
>  		ret = __trace_add_new_event(call, tr);
>  		if (ret < 0)
> -- 
> 2.47.2
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2025-07-19  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-19  2:31 Steven Rostedt
2025-07-19  4:36 ` Masami Hiramatsu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250719133634.f424cba37241e73b0f774a7f@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=Fusheng.Huang@luxshare-ict.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®