[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181112204918.2ba39252@vmware.local.home>
Date: Mon, 12 Nov 2018 20:49:18 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Alexander Popov <alex.popov@...ux.com>
Cc: kernel-hardening@...ts.openwall.com, Kees Cook <keescook@...omium.org>,
Jann Horn <jannh@...gle.com>, Ingo Molnar <mingo@...nel.org>, Andy
Lutomirski <luto@...nel.org>, Joerg Roedel <joro@...tes.org>, Borislav
Petkov <bp@...en8.de>, Thomas Gleixner <tglx@...utronix.de>, Dave Hansen
<dave.hansen@...ux.intel.com>, Peter Zijlstra <peterz@...radead.org>, Jan
Kara <jack@...e.cz>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Dan Williams <dan.j.williams@...el.com>, Masahiro Yamada
<yamada.masahiro@...ionext.com>, Masami Hiramatsu <mhiramat@...nel.org>,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] stackleak: Disable function tracing and kprobes for
stackleak_erase()
On Tue, 13 Nov 2018 00:08:48 +0300
Alexander Popov <alex.popov@...ux.com> wrote:
> The stackleak_erase() function is called on the trampoline stack at the end
> of syscall. This stack is not big enough for ftrace and kprobes operations,
> e.g. it can be exhausted if we use kprobe_events for stackleak_erase().
>
> So let's disable function tracing and kprobes for stackleak_erase().
>
> Reported-by: kernel test robot <lkp@...el.com>
> Signed-off-by: Alexander Popov <alex.popov@...ux.com>
>
Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
-- 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.
