Date: Mon, 12 Nov 2018 12:21:48 -0500 From: Steven Rostedt Subject: Re: [PATCH 1/1] stackleak: Disable ftrace for stackleak.c Message-ID: <20181112122148.0fab4c7f@vmware.local.home> In-Reply-To: <31b45d77-7b49-3984-a1e5-17993f50eee3@linux.com> References: <1541887530-16610-1-git-send-email-alex.popov@linux.com> <20181110183011.2290fc20@gandalf.local.home> <20181111205351.1874bb1e@vmware.local.home> <20181112115058.39e98750750c91eeb349cfdf@kernel.org> <31b45d77-7b49-3984-a1e5-17993f50eee3@linux.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: Alexander Popov Cc: Masami Hiramatsu , kernel-hardening@lists.openwall.com, Kees Cook , Jann Horn , Ingo Molnar , Andy Lutomirski , Joerg Roedel , Borislav Petkov , Thomas Gleixner , Dave Hansen , Peter Zijlstra , Jan Kara , Mathieu Desnoyers , Dan Williams , Masahiro Yamada , x86@kernel.org, linux-kernel@vger.kernel.org List-ID: On Mon, 12 Nov 2018 19:51:00 +0300 Alexander Popov wrote: > By the way, are there any other tracing/instrumentation mechanisms that should > be disabled? ftrace and kprobes are pretty much the only ones that currently do self modification of code all over the kernel. Kprobes even more so than ftrace. -- Steve