public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/user_events: Hold event_mutex during dyn_event_add
Date: Tue, 29 Mar 2022 09:47:52 +0900	[thread overview]
Message-ID: <20220329094752.d0950054058846197f573349@kernel.org> (raw)
In-Reply-To: <20220328223225.1992-1-beaub@linux.microsoft.com>

On Mon, 28 Mar 2022 15:32:25 -0700
Beau Belgrave <beaub@linux.microsoft.com> wrote:

> Make sure the event_mutex is properly held during dyn_event_add call.
> This is required when adding dynamic events.
> 

Good catch!

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

Thank you,

> Reported-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>
> ---
>  kernel/trace/trace_events_user.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
> index 8b3d241a31c2..61d78d64bdf0 100644
> --- a/kernel/trace/trace_events_user.c
> +++ b/kernel/trace/trace_events_user.c
> @@ -1165,11 +1165,11 @@ static int user_event_parse(char *name, char *args, char *flags,
>  #endif
>  
>  	mutex_lock(&event_mutex);
> +
>  	ret = user_event_trace_register(user);
> -	mutex_unlock(&event_mutex);
>  
>  	if (ret)
> -		goto put_user;
> +		goto put_user_lock;
>  
>  	user->index = index;
>  
> @@ -1181,8 +1181,12 @@ static int user_event_parse(char *name, char *args, char *flags,
>  	set_bit(user->index, page_bitmap);
>  	hash_add(register_table, &user->node, key);
>  
> +	mutex_unlock(&event_mutex);
> +
>  	*newuser = user;
>  	return 0;
> +put_user_lock:
> +	mutex_unlock(&event_mutex);
>  put_user:
>  	user_event_destroy_fields(user);
>  	user_event_destroy_validators(user);
> 
> base-commit: c87857e214862a125208a4b1a510839d0c5a1bd4
> -- 
> 2.25.1
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2022-03-29  0:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 22:32 [PATCH] tracing/user_events: Hold event_mutex during dyn_event_add Beau Belgrave
2022-03-29  0:47 ` 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=20220329094752.d0950054058846197f573349@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=beaub@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@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