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

On Sun, 11 Nov 2018 01:05:30 +0300
Alexander Popov <> wrote:

> The stackleak_erase() function is called on the trampoline stack at the
> end of syscall. This stack is not big enough for ftrace operations,
> e.g. it can be overflowed if we enable kprobe_events for stackleak_erase().

Is the issue with kprobes or with function tracing? Because this stops
function tracing which I only want disabled if function tracing itself
is an issue, not for other things that may use the function tracing

-- 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.