From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH -tip v2 0/3] kprobes: introduce nokprobe and updating blacklist
Date: Fri, 01 Nov 2013 11:25:30 +0000 [thread overview]
Message-ID: <20131101112530.14657.87835.stgit@kbuild-fedora.novalocal> (raw)
According to Ingo's suggestion, I've introduced 'nokprobe'
new annotation as like as 'notrace' annotation, since
__kprobes annotation is too confusing to mark non-kprobe
able functions.
I took 'nokprobe' instead of 'noprobe' since we already
have irq_set_noprobe() etc.
Also, I've found that putting probes on some functions
could lock or reboot the kernel. These two patches fix
those bugs by prohibiting probing such functions by
adding those to blacklist(kprobes.text).
In both cases, those functions are related to int3 handling
execution path. One is related to irqoff-tracer and the other
is related to notifier debug option.
Thank you,
Changes in the latest version:
- introduce nokprobe annotation
- change __kprobes to nokprobe in bugfixes
- remove unneeded linux/kprobes.h includings.
---
Masami Hiramatsu (3):
kprobes: Introduce nokprobe annotation for non-probe-able functions
[BUGFIX] kprobes/x86: Prohibit probing on debug_stack_*
[BUGFIX] kprobes: Prohibit probing on func_ptr_is_kernel_text
arch/x86/kernel/cpu/common.c | 6 +++---
include/linux/compiler.h | 6 ++++--
kernel/extable.c | 2 +-
3 files changed, 8 insertions(+), 6 deletions(-)
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next reply other threads:[~2013-11-01 11:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 11:25 Masami Hiramatsu [this message]
2013-11-01 11:25 ` [PATCH -tip v2 1/3] kprobes: Introduce nokprobe annotation for non-probe-able functions Masami Hiramatsu
2013-11-01 13:55 ` Steven Rostedt
2013-11-05 1:45 ` Masami Hiramatsu
2013-11-01 11:25 ` [PATCH -tip v2 2/3] [BUGFIX] kprobes/x86: Prohibit probing on debug_stack_* Masami Hiramatsu
2013-11-01 13:56 ` Steven Rostedt
2013-11-01 11:25 ` [PATCH -tip v2 3/3] [BUGFIX] kprobes: Prohibit probing on func_ptr_is_kernel_text Masami Hiramatsu
2013-11-01 13:57 ` Steven Rostedt
2013-11-05 2:00 ` Steven Rostedt
2013-11-05 3:15 ` Masami Hiramatsu
2013-11-05 6:09 ` Ingo Molnar
2013-11-05 6:59 ` Masami Hiramatsu
2013-11-05 7:05 ` Ingo Molnar
2013-11-05 11:38 ` Masami Hiramatsu
2013-11-05 12:35 ` Masami Hiramatsu
2013-11-06 6:07 ` Ingo Molnar
2013-11-06 10:34 ` Masami Hiramatsu
2013-11-06 11:50 ` Ingo Molnar
2013-11-06 12:21 ` Steven Rostedt
2013-11-05 13:13 ` Steven Rostedt
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=20131101112530.14657.87835.stgit@kbuild-fedora.novalocal \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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®