From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 12 Nov 2018 20:49:18 -0500 From: Steven Rostedt Subject: Re: [PATCH 1/1] stackleak: Disable function tracing and kprobes for stackleak_erase() Message-ID: <20181112204918.2ba39252@vmware.local.home> In-Reply-To: <1542056928-10917-1-git-send-email-alex.popov@linux.com> References: <1542056928-10917-1-git-send-email-alex.popov@linux.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: Alexander Popov Cc: kernel-hardening@lists.openwall.com, 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 , x86@kernel.org, linux-kernel@vger.kernel.org List-ID: On Tue, 13 Nov 2018 00:08:48 +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 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 > Signed-off-by: Alexander Popov > Reviewed-by: Steven Rostedt (VMware) -- Steve