From: Miroslav Benes <mbenes@suse.cz>
To: Song Liu <song@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>,
bpf@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
live-patching@vger.kernel.org, jolsa@kernel.org,
mhiramat@kernel.org, jpoimboe@kernel.org,
joe.lawrence@redhat.com, mark.rutland@arm.com, corbet@lwn.net,
stable@vger.kernel.org, linux-open-source@crowdstrike.com,
pmladek@suse.com
Subject: Re: [RFC PATCH bpf-next v3 2/2] selftests/livepatch: update test-ftrace.sh for deprecated ftrace_enabled
Date: Mon, 24 Aug 2026 14:41:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.2608241437380.17149@pobox.suse.cz> (raw)
In-Reply-To: <CAPhsuW5bW-xogJESb=ydUMH-ZjczoTP9JbuwPJZgbGZBzv-1CA@mail.gmail.com>
> > We do not deprecate features. tracefs code is user API. We do not break
> > user space. The ftrace_enabled is something that is being removed because
> > it is broken to begin with. In fact, if we find out that anything depends
> > on ftrace_enabled, we need to revert the change that disabled it.
> >
> > The removal of ftrace_enabled is the exception and not the rule.
>
> Agreed that ftrace APIs need to be very stable, as there are many out
> of tree users. OTOH, I think livepatch can afford breaking some
> compatibility.
We discussed that a bit in the context of this patch set [1]. I think it
is valuable to have the kselftests backward compatibility but there is of
course some limit to it. We can talk about it at Plumbers during the
backward compatibility session as well [2].
Miroslav
[1] https://lore.kernel.org/all/20260413-lp-tests-old-fixes-v2-0-367c7cb5006f@suse.com/
[2] https://lpc.events/event/20/contributions/2530/
next prev parent reply other threads:[~2026-08-24 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 15:29 [RFC PATCH bpf-next v3 0/2] ftrace: deprecate the ftrace_enabled disable switch Andrey Grodzovsky
2026-08-06 15:29 ` [RFC PATCH bpf-next v3 1/2] ftrace: deprecate disabling via ftrace_enabled sysctl Andrey Grodzovsky
2026-08-06 21:21 ` Song Liu
2026-08-06 21:52 ` Andrey Grodzovsky
2026-08-09 18:32 ` Andrey Grodzovsky
2026-08-24 12:27 ` Miroslav Benes
2026-08-24 12:30 ` Miroslav Benes
2026-08-06 15:30 ` [RFC PATCH bpf-next v3 2/2] selftests/livepatch: update test-ftrace.sh for deprecated ftrace_enabled Andrey Grodzovsky
2026-08-06 21:18 ` Song Liu
2026-08-06 21:45 ` Andrey Grodzovsky
2026-08-07 0:51 ` Steven Rostedt
2026-08-07 7:17 ` Song Liu
2026-08-07 12:42 ` Steven Rostedt
2026-08-07 16:16 ` Song Liu
2026-08-24 12:41 ` Miroslav Benes [this message]
2026-08-24 12:41 ` Miroslav Benes
2026-08-25 13:12 ` Petr Mladek
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=alpine.LSU.2.21.2608241437380.17149@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=joe.lawrence@redhat.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=song@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