Messages in this thread | | | Date | Tue, 13 Nov 2018 10:21:45 -0800 | From | Masami Hiramatsu <> | Subject | Re: [PATCH 1/1] stackleak: Disable ftrace for stackleak.c |
| |
On Mon, 12 Nov 2018 12:21:48 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 12 Nov 2018 19:51:00 +0300 > Alexander Popov <alex.popov@linux.com> 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.
Right, since kprobes uses int3 or sw breakpoint exception for hooking into the code, it consumes stack much more.
Thank you,
-- Masami Hiramatsu <mhiramat@kernel.org>
| |