Linux Trace Kernel
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Yash Suthar <yashsuthar983@gmail.com>,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	skhan@linuxfoundation.org
Subject: Re: [PATCH] tracing: Replace BUG_ON with lockdep_assert_held in uprobe_buffer functions
Date: Mon, 25 May 2026 16:42:10 +0900	[thread overview]
Message-ID: <20260525164210.9885d1eef078547290ead1df@kernel.org> (raw)
In-Reply-To: <20260521181601.77ce38e6@gandalf.local.home>

On Thu, 21 May 2026 18:16:01 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Fri, 22 May 2026 00:58:46 +0530
> Yash Suthar <yashsuthar983@gmail.com> wrote:
> 
> > Replace BUG_ON(!mutex_is_locked(&event_mutex)) with
> > lockdep_assert_held(&event_mutex) in uprobe_buffer_enable() and
> > uprobe_buffer_disable().
> > 
> > BUG_ON() will crash the kernel. mutex_is_locked() only checks
> > if any task holds lock,but not the caller task. lockdep_assert_held()
> > also check current task for lock and no crash on true condition.
> > 
> > Signed-off-by: Yash Suthar <yashsuthar983@gmail.com>
> 
> This looks good to me.
> 
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> 
> Masami, do you want to take this?

Yeah, let me pick this.

Thanks!

> 
> -- Steve
> 
> > ---
> >  kernel/trace/trace_uprobe.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
> > index 2cabf8a23ec5..aee0960d0cf7 100644
> > --- a/kernel/trace/trace_uprobe.c
> > +++ b/kernel/trace/trace_uprobe.c
> > @@ -912,7 +912,7 @@ static int uprobe_buffer_enable(void)
> >  {
> >  	int ret = 0;
> >  
> > -	BUG_ON(!mutex_is_locked(&event_mutex));
> > +	lockdep_assert_held(&event_mutex);
> >  
> >  	if (uprobe_buffer_refcnt++ == 0) {
> >  		ret = uprobe_buffer_init();
> > @@ -927,7 +927,7 @@ static void uprobe_buffer_disable(void)
> >  {
> >  	int cpu;
> >  
> > -	BUG_ON(!mutex_is_locked(&event_mutex));
> > +	lockdep_assert_held(&event_mutex);
> >  
> >  	if (--uprobe_buffer_refcnt == 0) {
> >  		for_each_possible_cpu(cpu)
> 
> 


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

      reply	other threads:[~2026-05-25  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 19:28 [PATCH] tracing: Replace BUG_ON with lockdep_assert_held in uprobe_buffer functions Yash Suthar
2026-05-21 22:16 ` Steven Rostedt
2026-05-25  7:42   ` 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=20260525164210.9885d1eef078547290ead1df@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yashsuthar983@gmail.com \
    /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