From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Shuah Khan <shuah@kernel.org>, Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/2] selftests: tracing: Use mutex_unlock for testing glob filter
Date: Fri, 4 Jul 2025 15:04:25 +0900 [thread overview]
Message-ID: <20250704150425.a8a82c7768e1c99ee272e585@kernel.org> (raw)
In-Reply-To: <20250703103039.3559a7e1@batman.local.home>
Shuah,
Can you take this patch (fix) to your tree since this is
a fix for the selftest?
Thank you,
On Thu, 3 Jul 2025 10:30:39 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 3 Jul 2025 13:26:43 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Since commit c5b6ababd21a ("locking/mutex: implement
> > mutex_trylock_nested") makes mutex_trylock() as an inlined
> > function if CONFIG_DEBUG_LOCK_ALLOC=y, we can not use
> > mutex_trylock() for testing the glob filter of ftrace.
> >
> > Use mutex_unlock instead.
> >
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-07-04 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 4:26 [PATCH 0/2] tracing: Fixes for filter Masami Hiramatsu (Google)
2025-07-03 4:26 ` [PATCH 1/2] tracing: Handle "(const) char __attribute() *" as string ptr type Masami Hiramatsu (Google)
2025-07-08 1:06 ` Masami Hiramatsu
2025-07-03 4:26 ` [PATCH 2/2] selftests: tracing: Use mutex_unlock for testing glob filter Masami Hiramatsu (Google)
2025-07-03 14:30 ` Steven Rostedt
2025-07-04 6:04 ` Masami Hiramatsu [this message]
2025-07-07 21:36 ` Shuah Khan
2025-07-03 14:30 ` [PATCH 0/2] tracing: Fixes for filter Steven Rostedt
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=20250704150425.a8a82c7768e1c99ee272e585@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.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®