|
Message-ID: <20181112115228.1c747426@vmware.local.home> Date: Mon, 12 Nov 2018 11:52:28 -0500 From: Steven Rostedt <rostedt@...dmis.org> To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Cc: Masami Hiramatsu <mhiramat@...nel.org>, Alexander Popov <alex.popov@...ux.com>, kernel-hardening <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>, Dan Williams <dan.j.williams@...el.com>, Masahiro Yamada <yamada.masahiro@...ionext.com>, x86 <x86@...nel.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/1] stackleak: Disable ftrace for stackleak.c On Mon, 12 Nov 2018 09:53:29 -0500 (EST) Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote: > Just to clarify: AFAIU you guys are recommending to add _both_ a "notrace" > annotation to stackleak_erase() _and_ a NOKPROBE_SYMBOL(stackleak_erase), > so neither function tracing nor kprobes can hook on that function. Correct. -- 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.