From: Petr Mladek <pmladek@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: [PATCH 0/4] ftrace: One more check on x86 and some small fixes
Date: Mon, 27 Jun 2016 15:54:33 +0200 [thread overview]
Message-ID: <1467035677-12193-1-git-send-email-pmladek@suse.com> (raw)
1st patch adds one more paranoid check of the modified function on x86.
Plus there are 3 small changes that appeared when hunting down
the 1st patch.
Petr Mladek (4):
ftrace/x86: Make sure to modify 5-bite instructions
ftrace/x86: Do not crash when reading wrong ftrace func
ftrace: Always destroy trampoline when shutting down the trace
ftrace: Fixup trace_selftest_ops()
arch/x86/kernel/ftrace.c | 12 ++++++++-
kernel/trace/ftrace.c | 62 ++++++++++++++++++++++---------------------
kernel/trace/trace_selftest.c | 7 ++---
3 files changed, 47 insertions(+), 34 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-06-27 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 13:54 Petr Mladek [this message]
2016-06-27 13:54 ` [PATCH 1/4] ftrace/x86: Make sure to modify 5-bite instructions Petr Mladek
2016-06-27 13:54 ` [PATCH 2/4] ftrace/x86: Do not crash when reading wrong ftrace func Petr Mladek
2016-06-27 14:48 ` Steven Rostedt
2016-06-28 10:00 ` Petr Mladek
2016-06-27 13:54 ` [PATCH 3/4] ftrace: Always destroy trampoline when shutting down the trace Petr Mladek
2016-06-27 13:54 ` [PATCH 4/4] ftrace: Fixup trace_selftest_ops() Petr Mladek
2016-06-28 5:22 ` [PATCH 0/4] ftrace: One more check on x86 and some small fixes Namhyung Kim
2016-06-28 19:17 ` Steven Rostedt
2016-06-29 8:22 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1467035677-12193-1-git-send-email-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=fweisbec@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®