On Thu, 06 Aug 2026 11:29:59 -0400, Andrey Grodzovsky <[email protected]> wrote: > Writing 0 to kernel.ftrace_enabled has not reliably disabled ftrace > for years (FTRACE_OPS_FL_PERMANENT users already block it, and more > callers rely on ftrace always being on). Refuse the write instead of > leaving it in an inconsistent "disables some, not all" state: return > -EOPNOTSUPP and log a message. Reads and enabling (writing 1) are > unaffected. > > [...]
Reviewed-by: Miroslav Benes <[email protected]> -- Miroslav
