summaryrefslogtreecommitdiffstats
path: root/arch/ppc64
diff options
context:
space:
mode:
authorJim Keniston <jkenisto@us.ibm.com>2005-09-06 15:19:34 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2005-09-07 16:58:01 -0700
commitbce0649417d6e71f6df8ab7b11103d247913b142 (patch)
tree529573458558f625f784f1f977a0d0a72e753e2b /arch/ppc64
parent661e5a3d9958dc83d610992da85625c0ada9bb06 (diff)
downloadblackbird-op-linux-bce0649417d6e71f6df8ab7b11103d247913b142.tar.gz
blackbird-op-linux-bce0649417d6e71f6df8ab7b11103d247913b142.zip
[PATCH] kprobes: fix handling of simultaneous probe hit/unregister
This patch fixes a bug in kprobes's handling of a corner case on i386 and x86_64. On an SMP system, if one CPU unregisters a kprobe just after another CPU hits that probepoint, kprobe_handler() on the latter CPU sees that the kprobe has been unregistered, and attempts to let the CPU continue as if the probepoint hadn't been hit. The bug is that on i386 and x86_64, we were neglecting to set the IP back to the beginning of the probed instruction. This could cause an oops or crash. This bug doesn't exist on ppc64 and ia64, where a breakpoint instruction leaves the IP pointing to the beginning of the instruction. I don't know about sparc64. (Dave, could you please advise?) This fix has been tested on i386 and x86_64 SMP systems. To reproduce the problem, set one CPU to work registering and unregistering a kprobe repeatedly, and another CPU pounding the probepoint in a tight loop. Acked-by: Prasanna S Panchamukhi <prasanna@in.ibm.com> Signed-off-by: Jim Keniston <jkenisto@us.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/ppc64')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud