From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sven Schnelle <svens@linux.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Fix unique symbol check in kprobe_non_uniq_symbol.tc
Date: Thu, 10 Sep 2026 09:01:02 +0900 [thread overview]
Message-ID: <20260910090102.5ba6c7993bc0a7bf1fbc4426@kernel.org> (raw)
In-Reply-To: <20260909134156.6425e8b0@gandalf.local.home>
On Wed, 9 Sep 2026 13:41:56 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 9 Sep 2026 11:29:53 +0200
> Sven Schnelle <svens@linux.ibm.com> wrote:
>
> > The current regex also matches symbols in modules, which makes the
> > test fail on s390 where name_show is present only once in the kernel,
> > but also multiple times in modules:
> >
> > 000001b1401cdc20 t name_show
> > 000001b0c05e6c40 t name_show [mdev]
> > 000001b0c0495f30 t name_show [i2c_core]
> >
> > Fix this by changing the regular expression to only match the function
> > name.
> >
> > Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
> > ---
> > .../selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc
> > index bc9514428dba..07b1177c1634 100644
> > --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc
> > @@ -6,7 +6,7 @@
> > SYMBOL='name_show'
> >
> > # We skip this test on kernel where SYMBOL is unique or does not exist.
> > -if [ "$(grep -c -E "[[:alnum:]]+ t ${SYMBOL}" /proc/kallsyms)" -le '1' ]; then
> > +if [ "$(grep -c -E "[[:alnum:]]+ t ${SYMBOL}$" /proc/kallsyms)" -le '1' ]; then
> > exit_unsupported
> > fi
> >
>
> Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
>
> But I wonder if "type_show" or "init_once" is a better option than
> "name_show"?
Yeah, we have many other candidates :)
$ grep -E '[[:alnum:]]+ t [[:alpha:]][[:alnum:]_]+$' /proc/kallsyms | cut -d " " -f 3 | sort | uniq -cd | sort -nr | head
27 p4d_offset
20 type_show
20 dev_attr_name
17 dev_attr_modalias
16 pfn_to_mfn
15 name_show
14 modalias_show
14 dev_attr_type
13 init_once
13 format_attr_event
Maybe we can just fallback to this logic for finding available symbols?
Thanks,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-09-10 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 9:29 [PATCH] selftests/ftrace: Fix unique symbol check in kprobe_non_uniq_symbol.tc Sven Schnelle
2026-09-09 17:41 ` Steven Rostedt
2026-09-10 0:01 ` Masami Hiramatsu [this message]
2026-09-09 23:41 ` Masami Hiramatsu
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=20260910090102.5ba6c7993bc0a7bf1fbc4426@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 \
--cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.