[PATCH] Fix kprobes handling of simultaneous probe hit/unregister
From: Jim Keniston (jkenisto_at_us.ibm.com)
Date: 08/31/05
- Previous message: Zachary Amsden: "[PATCH 1/2] Whitespace cleanup in pageattr.c"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: LKML <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org> Date: 31 Aug 2005 14:53:37 -0700
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.
Please apply.
Acked-by: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Signed-off-by: Jim Keniston <jkenisto@us.ibm.com>
--- linux-2.6.13/arch/i386/kernel/kprobes.c 2005-08-30 12:27:35.000000000 -0700
+++ linux-fixed/arch/i386/kernel/kprobes.c 2005-08-30 15:33:03.000000000 -0700
@@ -220,7 +220,10 @@
* either a probepoint or a debugger breakpoint
* at this address. In either case, no further
* handling of this interrupt is appropriate.
+ * Back up over the (now missing) int3 and run
+ * the original instruction.
*/
+ regs->eip -= sizeof(kprobe_opcode_t);
ret = 1;
}
/* Not one of ours: let kernel handle it */
--- linux-2.6.13/arch/x86_64/kernel/kprobes.c 2005-08-30 12:27:35.000000000 -0700
+++ linux-fixed/arch/x86_64/kernel/kprobes.c 2005-08-30 15:32:31.000000000 -0700
@@ -360,7 +360,10 @@
* either a probepoint or a debugger breakpoint
* at this address. In either case, no further
* handling of this interrupt is appropriate.
+ * Back up over the (now missing) int3 and run
+ * the original instruction.
*/
+ regs->rip = (unsigned long)addr;
ret = 1;
}
/* Not one of ours: let kernel handle it */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Zachary Amsden: "[PATCH 1/2] Whitespace cleanup in pageattr.c"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Server Crash (2.6.17-1.2157)- BUG: soft lockup detected on CPU#3!
... I just installed Fedora Core Kernel 2.6.17-1.2157_FC5smp and immediately got a "BUG:
soft lockup detected on CPU#3!", I've never had this on any other kernel version before, but on my desk
top PC and now this server with this specific kernel. ... isg-dev7 kernel: CPU: 3 ...
kernel BUG at include/linux/list.h:185! ... MEM window: dd200000-dd3fffff ...
(Fedora) - Re: Why choose Kerio instead of ZA?
... bug fixed: parallel resolving of many addresses caused crash of GUI ... I just
checked and KPF2 has one process using neglegible CPU ... I did notice that KPF4
is constantly reading and writing to the network via ... I browsed the Web using Windows Explorer.
... (comp.security.firewalls) - Re: possible CPU bug and request for Intel contacts
... Here are the details about CPU bug I mentioned in my previous post. ... kernel
code and mapped user space pages overlap. ... (Linux-Kernel) - [PATCH] Fix SMP alternatives : use mutex instead of spinlock, text_poke is sleepable
... I was using vanilla kernel (smp_alt is still a spinlock). ... Fix
SMP alternatives: use mutex instead of spinlock, ... CPU 1 is now offline ...
BUG: sleeping function called from invalid context at mm/slab.c:3053 ... (Linux-Kernel) - Re: crashme fault
... I'm really starting to suspect some early EM64T bug, ... the CPU claimed
it was a user access or not, ... goto good_area; ... (Linux-Kernel)