From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: ppcdev <linuxppc-dev@lists.ozlabs.org>,
oleg@redhat.com, Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: [PATCH 3/3] uprobes/powerpc: ignore trap variants during register
Date: Fri, 22 Mar 2013 17:16:24 +0530 [thread overview]
Message-ID: <20130322114624.GI26183@in.ibm.com> (raw)
In-Reply-To: <20130322114446.GG26183@in.ibm.com>
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
The current implementation of uprobes assumes that uprobes always wins
even when a register request is at a location with a conditional
breakpoint by some other entity. Refer to [1] for more details.
Remove the breakpoint instruction check during registration on powerpc,
so that uprobes behavior on powerpc matches that of x86.
[1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-March/104771.html
Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
---
arch/powerpc/kernel/uprobes.c | 6 ------
1 file changed, 6 deletions(-)
Index: linux-3.9-rc3/arch/powerpc/kernel/uprobes.c
===================================================================
--- linux-3.9-rc3.orig/arch/powerpc/kernel/uprobes.c
+++ linux-3.9-rc3/arch/powerpc/kernel/uprobes.c
@@ -53,12 +53,6 @@ int arch_uprobe_analyze_insn(struct arch
if (addr & 0x03)
return -EINVAL;
- /*
- * We currently don't support a uprobe on an already
- * existing breakpoint instruction underneath
- */
- if (is_trap(auprobe->ainsn))
- return -ENOTSUPP;
return 0;
}
next prev parent reply other threads:[~2013-03-22 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 11:44 [PATCH 1/3] uprobes: add trap variant helper Ananth N Mavinakayanahalli
2013-03-22 11:45 ` [PATCH 2/3] uprobes/powerpc: teach uprobes to ignore gdb breakpoints Ananth N Mavinakayanahalli
2013-03-22 11:46 ` Ananth N Mavinakayanahalli [this message]
2013-03-22 14:54 ` [PATCH 1/3] uprobes: add trap variant helper Oleg Nesterov
2013-03-22 15:07 ` Ananth N Mavinakayanahalli
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=20130322114624.GI26183@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oleg@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).