From: Filipe Xavier <felipeaggger@gmail.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Shuah Khan <shuah@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Felipe Xavier <felipe_life@live.com>
Subject: Re: [PATCH v2] selftests: livepatch: test if ftrace can trace a livepatched function
Date: Thu, 6 Mar 2025 19:12:32 -0300 [thread overview]
Message-ID: <b2637bad-9022-496a-9b83-0d348a6350b4@gmail.com> (raw)
In-Reply-To: <20250111-ftrace-selftest-livepatch-v2-1-9f4ff90f251a@gmail.com>
On 1/11/25 3:42 PM, Filipe Xavier wrote:
> This new test makes sure that ftrace can trace a
> function that was introduced by a livepatch.
>
> Signed-off-by: Filipe Xavier <felipeaggger@gmail.com>
> ---
> Changes in v2:
> - functions.sh: added reset tracing on push and pop_config.
> - test-ftrace.sh: enabled tracing_on before test init.
> - nitpick: added double quotations on filenames and fixed some wording.
> - Link to v1: https://lore.kernel.org/r/20250102-ftrace-selftest-livepatch-v1-1-84880baefc1b@gmail.com
> ---
> tools/testing/selftests/livepatch/functions.sh | 14 ++++++++++
> tools/testing/selftests/livepatch/test-ftrace.sh | 33 ++++++++++++++++++++++++
> 2 files changed, 47 insertions(+)
>
> diff --git a/tools/testing/selftests/livepatch/functions.sh b/tools/testing/selftests/livepatch/functions.sh
> index e5d06fb402335d85959bafe099087effc6ddce12..e6c13514002dae5f8d7461f90b8241ab43024ea4 100644
> --- a/tools/testing/selftests/livepatch/functions.sh
> +++ b/tools/testing/selftests/livepatch/functions.sh
> @@ -62,6 +62,9 @@ function push_config() {
> awk -F'[: ]' '{print "file " $1 " line " $2 " " $4}')
> FTRACE_ENABLED=$(sysctl --values kernel.ftrace_enabled)
> KPROBE_ENABLED=$(cat "$SYSFS_KPROBES_DIR/enabled")
> + TRACING_ON=$(cat "$SYSFS_DEBUG_DIR/tracing/tracing_on")
> + CURRENT_TRACER=$(cat "$SYSFS_DEBUG_DIR/tracing/current_tracer")
> + FTRACE_FILTER=$(cat "$SYSFS_DEBUG_DIR/tracing/set_ftrace_filter")
> }
>
> function pop_config() {
> @@ -74,6 +77,17 @@ function pop_config() {
> if [[ -n "$KPROBE_ENABLED" ]]; then
> echo "$KPROBE_ENABLED" > "$SYSFS_KPROBES_DIR/enabled"
> fi
> + if [[ -n "$TRACING_ON" ]]; then
> + echo "$TRACING_ON" > "$SYSFS_DEBUG_DIR/tracing/tracing_on"
> + fi
> + if [[ -n "$CURRENT_TRACER" ]]; then
> + echo "$CURRENT_TRACER" > "$SYSFS_DEBUG_DIR/tracing/current_tracer"
> + fi
> + if [[ "$FTRACE_FILTER" == *"#"* ]]; then
> + echo > "$SYSFS_DEBUG_DIR/tracing/set_ftrace_filter"
> + elif [[ -n "$FTRACE_FILTER" ]]; then
> + echo "$FTRACE_FILTER" > "$SYSFS_DEBUG_DIR/tracing/set_ftrace_filter"
> + fi
> }
>
> function set_dynamic_debug() {
> diff --git a/tools/testing/selftests/livepatch/test-ftrace.sh b/tools/testing/selftests/livepatch/test-ftrace.sh
> index fe14f248913acbec46fb6c0fec38a2fc84209d39..66af5d726c52e48e5177804e182b4ff31784d5ac 100755
> --- a/tools/testing/selftests/livepatch/test-ftrace.sh
> +++ b/tools/testing/selftests/livepatch/test-ftrace.sh
> @@ -61,4 +61,37 @@ livepatch: '$MOD_LIVEPATCH': unpatching complete
> % rmmod $MOD_LIVEPATCH"
>
>
> +# - verify livepatch can load
> +# - check if traces have a patched function
> +# - unload livepatch and reset trace
> +
> +start_test "trace livepatched function and check that the live patch remains in effect"
> +
> +TRACE_FILE="$SYSFS_DEBUG_DIR/tracing/trace"
> +FUNCTION_NAME="livepatch_cmdline_proc_show"
> +
> +load_lp $MOD_LIVEPATCH
> +
> +echo 1 > "$SYSFS_DEBUG_DIR/tracing/tracing_on"
> +echo $FUNCTION_NAME > "$SYSFS_DEBUG_DIR/tracing/set_ftrace_filter"
> +echo "function" > "$SYSFS_DEBUG_DIR/tracing/current_tracer"
> +echo "" > "$TRACE_FILE"
> +
> +if [[ "$(cat /proc/cmdline)" != "$MOD_LIVEPATCH: this has been live patched" ]] ; then
> + echo -e "FAIL\n\n"
> + die "livepatch kselftest(s) failed"
> +fi
> +
> +grep -q $FUNCTION_NAME "$TRACE_FILE"
> +FOUND=$?
> +
> +disable_lp $MOD_LIVEPATCH
> +unload_lp $MOD_LIVEPATCH
> +
> +if [ "$FOUND" -eq 1 ]; then
> + echo -e "FAIL\n\n"
> + die "livepatch kselftest(s) failed"
> +fi
> +
> +
> exit 0
>
> ---
> base-commit: fc033cf25e612e840e545f8d5ad2edd6ba613ed5
> change-id: 20250101-ftrace-selftest-livepatch-161fb77dbed8
>
> Best regards,
Hi Folks, sorry for the delay... thanks everyone for the feedback's.
I applied almost all the requested adjustments, except this one:
> echo '!*:traceoff' > "$SYSFS_TRACING_DIR/set_ftrace_filter"
causes this error: "echo: write error: no such device"
> echo "" > "$SYSFS_TRACING_DIR/current_tracer"
causes this error: "echo: write error: invalid argument"
I sent a new patchSet(splited) to the list.
Cheers,
Filipe Xavier
prev parent reply other threads:[~2025-03-06 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 18:42 [PATCH v2] selftests: livepatch: test if ftrace can trace a livepatched function Filipe Xavier
2025-01-14 17:18 ` Marcos Paulo de Souza
2025-01-15 15:03 ` Joe Lawrence
2025-01-15 15:31 ` Petr Mladek
2025-03-06 22:12 ` Filipe Xavier [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=b2637bad-9022-496a-9b83-0d348a6350b4@gmail.com \
--to=felipeaggger@gmail.com \
--cc=felipe_life@live.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=pmladek@suse.com \
--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