[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180726104029.7736-1-nstange@suse.de>
Date: Thu, 26 Jul 2018 12:40:28 +0200
From: Nicolai Stange <nstange@...e.de>
To: Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jiri Kosina <jikos@...nel.org>,
Miroslav Benes <mbenes@...e.cz>,
Petr Mladek <pmladek@...e.com>,
Nicolai Stange <nstange@...e.de>,
live-patching@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/1] x86/ftrace: fix live patching vs. tracing race
Hi,
if a user starts to trace a live patched function, its mcount call will get
redirected from a trampoline to ftrace_regs_caller.
In preparation for that, ftrace on x86 first installs an int3 insn at that
call site.
ftrace_int3_handler() in turn simply skips over the mcount call insn,
effectively reverting the livepatch for that function during
ftrace_replace_code().
This breaks KLP's consistency model.
There are two possible options for fixing this:
1.) At the ftrace level.
2.) Search for a matching klp_ops from ftrace_int3_handler() and
handle the redirection if needed.
Both have their drawbacks, hence the RFC mode for this patch implementing
1.).
The main disadvantage is that it doesn't work on 32 bits (c.f. the patch
description), but for KLP this would be fine.
OTOH, it keeps KLP specific code out of ftrace_int3_handler() and might
perhaps be beneficial in other contexts as well.
Thanks for your comments!
Nicolai
Nicolai Stange (1):
x86/ftrace: make ftrace_int3_handler() not to skip fops invocation
arch/x86/kernel/ftrace.c | 48 ++++++++++++++++++++++++++++++++------
arch/x86/kernel/ftrace_64.S | 56 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 97 insertions(+), 7 deletions(-)
--
2.13.7
Powered by blists - more mailing lists