[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27ee573f55de645f78969fd9a30cb53bca219144.camel@kernel.org>
Date: Wed, 03 Dec 2025 16:38:13 -0600
From: Tom Zanussi <zanussi@...nel.org>
To: Steven Rostedt <rostedt@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Mark Rutland
<mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2 1/3] tracing: Remove unneeded event_mutex lock in
event_trigger_regex_release()
On Tue, 2025-11-25 at 16:40 -0500, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@...dmis.org>
>
> In event_trigger_regex_release(), the only code is:
>
> mutex_lock(&event_mutex);
> if (file->f_mode & FMODE_READ)
> seq_release(inode, file);
> mutex_unlock(&event_mutex);
>
> return 0;
>
> There's nothing special about the file->f_mode or the seq_release()
> that
> requires any locking. Remove the unnecessary locks.
>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
> Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
Looks good to me.
Reviewed-by: Tom Zanussi <zanussi@...nel.org>
> ---
> kernel/trace/trace_events_trigger.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/kernel/trace/trace_events_trigger.c
> b/kernel/trace/trace_events_trigger.c
> index 7795af600466..e5dcfcbb2cd5 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -314,13 +314,9 @@ static ssize_t event_trigger_regex_write(struct
> file *file,
>
> static int event_trigger_regex_release(struct inode *inode, struct
> file *file)
> {
> - mutex_lock(&event_mutex);
> -
> if (file->f_mode & FMODE_READ)
> seq_release(inode, file);
>
> - mutex_unlock(&event_mutex);
> -
> return 0;
> }
>
Powered by blists - more mailing lists