Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Nov 2018 12:21:48 -0500
From: Steven Rostedt <>
To: Alexander Popov <>
Cc: Masami Hiramatsu <>,, 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
Subject: Re: [PATCH 1/1] stackleak: Disable ftrace for stackleak.c

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

-- Steve

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.