From: Pratyush Anand <panand@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: oleg@redhat.com, srikar@linux.vnet.ibm.com,
Pratyush Anand <panand@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH] uprobe: Add uprobe_pre/post_sstep_notifier to NOKPROBE_SYMBOL
Date: Tue, 2 Aug 2016 12:14:06 +0530 [thread overview]
Message-ID: <66dfa2cb82fc306d42e51adf0f5d819b4695644e.1470120173.git.panand@redhat.com> (raw)
uprobe_pre_sstep_notifier and uprobe_post_sstep_notifier are called from
debug exception handler, so blacklist them for kprobing.
Signed-off-by: Pratyush Anand <panand@redhat.com>
---
kernel/events/uprobes.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index b7a525ab2083..206e594cb65e 100644
--- a/kernel/events/uprobes.c
+++ b/kernel/events/uprobes.c
@@ -37,6 +37,7 @@
#include <linux/percpu-rwsem.h>
#include <linux/task_work.h>
#include <linux/shmem_fs.h>
+#include <linux/kprobes.h>
#include <linux/uprobes.h>
@@ -1997,6 +1998,7 @@ int uprobe_pre_sstep_notifier(struct pt_regs *regs)
set_thread_flag(TIF_UPROBE);
return 1;
}
+NOKPROBE_SYMBOL(uprobe_pre_sstep_notifier);
/*
* uprobe_post_sstep_notifier gets called in interrupt context as part of notifier
@@ -2014,6 +2016,7 @@ int uprobe_post_sstep_notifier(struct pt_regs *regs)
set_thread_flag(TIF_UPROBE);
return 1;
}
+NOKPROBE_SYMBOL(uprobe_post_sstep_notifier);
static struct notifier_block uprobe_exception_nb = {
.notifier_call = arch_uprobe_exception_notify,
--
2.5.5
next reply other threads:[~2016-08-02 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 6:44 Pratyush Anand [this message]
2016-08-02 15:45 ` Masami Hiramatsu
2016-08-03 4:24 ` Pratyush Anand
2016-08-03 10:35 ` Pratyush Anand
2016-08-03 14:31 ` Masami Hiramatsu
2016-08-02 20:30 ` Oleg Nesterov
2016-08-03 4:12 ` Pratyush Anand
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=66dfa2cb82fc306d42e51adf0f5d819b4695644e.1470120173.git.panand@redhat.com \
--to=panand@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
/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®