Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 11 Nov 2018 13:19:45 +0300
From: Alexander Popov <>
To: Steven Rostedt <>
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 11.11.2018 2:30, Steven Rostedt wrote:
> 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
> infrastructure.

Hello Steven,

I believe that stackleak erasing is not compatible with function tracing itself.
That's what the kernel testing robot has hit:

I used kprobe_events just to reproduce the problem:

Best regards,

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.