From: Joe Lawrence <joe.lawrence@redhat.com>
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: bpf@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, rostedt@goodmis.org, mbenes@suse.cz,
corbet@lwn.net, jpoimboe@kernel.org, shuah@kernel.org,
jolsa@kernel.org, mhiramat@kernel.org, stable@vger.kernel.org,
linux-open-source@crowdstrike.com
Subject: Re: [RFC PATCH bpf-next v2 2/2] selftests/livepatch: update test-ftrace.sh for deprecated ftrace_enabled
Date: Fri, 31 Jul 2026 20:30:58 -0400 [thread overview]
Message-ID: <am0-QoUNQo4p2sBg@redhat.com> (raw)
In-Reply-To: <20260731175358.3542156-3-andrey.grodzovsky@crowdstrike.com>
On Fri, Jul 31, 2026 at 01:53:58PM -0400, Andrey Grodzovsky wrote:
> kernel.ftrace_enabled=0 is now refused on kernels that deprecate the
> knob, so the old disable/reload flow no longer applies there. Probe
> for this with ftrace_disable_supported() and keep the full original
> scenario (disable, fail to load a livepatch, re-enable, load, confirm
> disable is refused while loaded) on kernels where it still works;
> otherwise just confirm the write is refused.
>
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
> Suggested-by: Miroslav Benes <mbenes@suse.cz>
> Assisted-by: Claude:claude-sonnet-5
> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
> ---
> .../testing/selftests/livepatch/functions.sh | 13 ++++++
> .../selftests/livepatch/test-ftrace.sh | 45 ++++++++++++-------
> 2 files changed, 41 insertions(+), 17 deletions(-)
>
> diff --git a/tools/testing/selftests/livepatch/functions.sh b/tools/testing/selftests/livepatch/functions.sh
> index 30dc677b2f45..7fa4bda70221 100644
> --- a/tools/testing/selftests/livepatch/functions.sh
> +++ b/tools/testing/selftests/livepatch/functions.sh
> @@ -126,6 +126,19 @@ function set_ftrace_enabled() {
> echo "livepatch: kernel.ftrace_enabled = $result" > /dev/kmsg
> }
>
> +# ftrace_disable_supported() - probe whether kernel.ftrace_enabled=0
> +# can still disable ftrace on this kernel. Newer kernels deprecate
> +# the knob and always refuse the write with -EOPNOTSUPP.
> +function ftrace_disable_supported() {
> + local result
> +
> + sysctl -q kernel.ftrace_enabled=0 &> /dev/null
> + result=$(sysctl --values kernel.ftrace_enabled)
> + sysctl -q kernel.ftrace_enabled=1 &> /dev/null
> +
> + [[ "$result" == "0" ]]
> +}
Small nit: AFAICT, it doesn't really affect the test pattern, but it
would be a bit cleaner if this function restored the original value
instead of always turning it on, like (untested):
orig=$(sysctl --values kernel.ftrace_enabled)
sysctl -q kernel.ftrace_enabled=0 &> /dev/null
result=$(sysctl --values kernel.ftrace_enabled)
sysctl -q "kernel.ftrace_enabled=$orig" &> /dev/null
[[ "$result" == "0" ]]
--
Joe
prev parent reply other threads:[~2026-08-01 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:53 [RFC PATCH bpf-next v2 0/2] ftrace: deprecate the ftrace_enabled disable switch Andrey Grodzovsky
2026-07-31 17:53 ` [RFC PATCH bpf-next v2 1/2] ftrace: deprecate disabling via ftrace_enabled sysctl Andrey Grodzovsky
2026-07-31 17:53 ` [RFC PATCH bpf-next v2 2/2] selftests/livepatch: update test-ftrace.sh for deprecated ftrace_enabled Andrey Grodzovsky
2026-08-01 0:30 ` Joe Lawrence [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=am0-QoUNQo4p2sBg@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=stable@vger.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