From: Steven Rostedt <rostedt@goodmis.org>
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
bpf@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, song@kernel.org,
jolsa@kernel.org, naveen@kernel.org, davem@davemloft.net,
mhiramat@kernel.org, stable@vger.kernel.org,
linux-open-source@crowdstrike.com, mbenes@suse.cz
Subject: Re: [RFC PATCH bpf-next 0/3] ftrace, kprobes, bpf: mark trampoline/kprobe ftrace_ops permanent
Date: Wed, 29 Jul 2026 15:45:41 -0400 [thread overview]
Message-ID: <20260729154541.0099cb14@gandalf.local.home> (raw)
In-Reply-To: <CAOu3gNg6kNYp-Sc9Eme6yW7Nu7wV6hZ9=CG0eptROfhQ-H8nFA@mail.gmail.com>
On Wed, 29 Jul 2026 14:20:17 -0400
Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com> wrote:
> Should I also clean up the entire PERMANENT flag logic we now have and
> drop the flag itself?
No, because we may need it in the unlikely case that we need to revert the
disabling of ftrace_enabled code.
After so many years, we can drop that flag if nobody complains.
-- Steve
next prev parent reply other threads:[~2026-07-29 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 0:59 [RFC PATCH bpf-next 0/3] ftrace, kprobes, bpf: mark trampoline/kprobe ftrace_ops permanent Andrey Grodzovsky
2026-07-29 0:59 ` [RFC PATCH bpf-next 1/3] bpf: mark trampoline " Andrey Grodzovsky
2026-07-29 13:29 ` Jiri Olsa
2026-07-29 0:59 ` [RFC PATCH bpf-next 2/3] kprobes: mark ftrace-based kprobe ops permanent Andrey Grodzovsky
2026-07-29 0:59 ` [RFC PATCH bpf-next 3/3] selftests/bpf: add ftrace_permanent test Andrey Grodzovsky
2026-07-29 13:23 ` Jiri Olsa
2026-07-29 17:16 ` Andrey Grodzovsky
2026-07-29 17:38 ` Steven Rostedt
2026-07-29 14:41 ` [RFC PATCH bpf-next 0/3] ftrace, kprobes, bpf: mark trampoline/kprobe ftrace_ops permanent Steven Rostedt
2026-07-29 15:00 ` Andrey Grodzovsky
2026-07-29 15:31 ` Steven Rostedt
2026-07-29 15:47 ` Linus Torvalds
2026-07-29 17:32 ` Steven Rostedt
2026-07-29 17:53 ` Steven Rostedt
[not found] ` <CAOu3gNg6kNYp-Sc9Eme6yW7Nu7wV6hZ9=CG0eptROfhQ-H8nFA@mail.gmail.com>
2026-07-29 19:45 ` Steven Rostedt [this message]
2026-07-29 19:48 ` Andrey Grodzovsky
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=20260729154541.0099cb14@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jolsa@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=naveen@kernel.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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