From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: akpm@osdl.org, Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
anil.s.keshavamurthy@intel.com,
Prasanna S Panchamukhi <prasanna@in.ibm.com>
Subject: [BUG][PATCH]Kprobes - No probes on critical path
Date: Fri, 9 Dec 2005 11:28:53 -0800 [thread overview]
Message-ID: <20051209112852.A31972@unix-os.sc.intel.com> (raw)
[BUG][PATCH]Kprobes - No probes on critical path
For Kprobes critical path is the path from debug break exception
handler till the control reaches kprobes exception code. No probes
can be supported in this path as we will end up in recursion.
This patch prevents this by moving the below function to safe
__kprobes section onto which no probes can be inserted.
Please apply.
Signed-off-by: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
---------------------------------------------------------------
kernel/sys.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
Index: linux-2.6.15-rc5-mm1/kernel/sys.c
===================================================================
--- linux-2.6.15-rc5-mm1.orig/kernel/sys.c
+++ linux-2.6.15-rc5-mm1/kernel/sys.c
@@ -32,6 +32,7 @@
#include <linux/compat.h>
#include <linux/syscalls.h>
+#include <linux/kprobes.h>
#include <asm/uaccess.h>
#include <asm/io.h>
@@ -168,7 +169,7 @@ EXPORT_SYMBOL(notifier_chain_unregister)
* of the last notifier function called.
*/
-int notifier_call_chain(struct notifier_block **n, unsigned long val, void *v)
+int __kprobes notifier_call_chain(struct notifier_block **n, unsigned long val, void *v)
{
int ret=NOTIFY_DONE;
struct notifier_block *nb = *n;
reply other threads:[~2005-12-09 19:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051209112852.A31972@unix-os.sc.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=akpm@osdl.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.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®