From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sven Schnelle <svens@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Let fprobe test consider already enabled functions
Date: Wed, 26 Feb 2025 23:54:47 +0900 [thread overview]
Message-ID: <20250226235447.7fab8051b2968277ce6920db@kernel.org> (raw)
In-Reply-To: <20250226142703.910860-1-hca@linux.ibm.com>
On Wed, 26 Feb 2025 15:27:03 +0100
Heiko Carstens <hca@linux.ibm.com> wrote:
> The fprobe test fails on Fedora 41 since the fprobe test assumption that
> the number of enabled_functions is zero before the test starts is not
> necessarily true. Some user space tools, like systemd, add BPF programs
> that attach to functions. Those will show up in the enabled_functions table
> and must be taken into account by the fprobe test.
Hmm, this ftrace selftests has been expected to be run without
any BPF programs... Is there any other issue on other test cases?
Anyway, this looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you!
>
> Therefore count the number of lines of enabled_functions before tests
> start, and use that as base when comparing expected results.
>
> Fixes: e85c5e9792b9 ("selftests/ftrace: Update fprobe test to check enabled_functions file")
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> .../test.d/dynevent/add_remove_fprobe.tc | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_fprobe.tc b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_fprobe.tc
> index 449f9d8be746..73f6c6fcecab 100644
> --- a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_fprobe.tc
> +++ b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_fprobe.tc
> @@ -10,12 +10,16 @@ PLACE=$FUNCTION_FORK
> PLACE2="kmem_cache_free"
> PLACE3="schedule_timeout"
>
> +# Some functions may have BPF programs attached, therefore
> +# count already enabled_functions before tests start
> +ocnt=`cat enabled_functions | wc -l`
> +
> echo "f:myevent1 $PLACE" >> dynamic_events
>
> # Make sure the event is attached and is the only one
> grep -q $PLACE enabled_functions
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 1 ]; then
> +if [ $cnt -ne $((ocnt + 1)) ]; then
> exit_fail
> fi
>
> @@ -23,7 +27,7 @@ echo "f:myevent2 $PLACE%return" >> dynamic_events
>
> # It should till be the only attached function
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 1 ]; then
> +if [ $cnt -ne $((ocnt + 1)) ]; then
> exit_fail
> fi
>
> @@ -32,7 +36,7 @@ echo "f:myevent3 $PLACE2" >> dynamic_events
>
> grep -q $PLACE2 enabled_functions
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 2 ]; then
> +if [ $cnt -ne $((ocnt + 2)) ]; then
> exit_fail
> fi
>
> @@ -49,7 +53,7 @@ grep -q myevent1 dynamic_events
>
> # should still have 2 left
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 2 ]; then
> +if [ $cnt -ne $((ocnt + 2)) ]; then
> exit_fail
> fi
>
> @@ -57,7 +61,7 @@ echo > dynamic_events
>
> # Should have none left
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 0 ]; then
> +if [ $cnt -ne $ocnt ]; then
> exit_fail
> fi
>
> @@ -65,7 +69,7 @@ echo "f:myevent4 $PLACE" >> dynamic_events
>
> # Should only have one enabled
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 1 ]; then
> +if [ $cnt -ne $((ocnt + 1)) ]; then
> exit_fail
> fi
>
> @@ -73,7 +77,7 @@ echo > dynamic_events
>
> # Should have none left
> cnt=`cat enabled_functions | wc -l`
> -if [ $cnt -ne 0 ]; then
> +if [ $cnt -ne $ocnt ]; then
> exit_fail
> fi
>
> --
> 2.45.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-02-26 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:27 [PATCH] selftests/ftrace: Let fprobe test consider already enabled functions Heiko Carstens
2025-02-26 14:54 ` Masami Hiramatsu [this message]
2025-02-26 15:28 ` Heiko Carstens
2025-02-26 16:18 ` Steven Rostedt
2025-02-26 16:13 ` Steven Rostedt
2025-02-26 23:51 ` 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=20250226235447.7fab8051b2968277ce6920db@kernel.org \
--to=mhiramat@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox