Re: [PATCH -tip v8 08/26] kprobes/x86: Call exception handlers directly from do_int3/do_debug

2014-03-24 Thread Steven Rostedt
On Mon, 24 Mar 2014 17:47:06 +0900 Masami Hiramatsu wrote: > >> @@ -857,7 +857,7 @@ no_change: > >> * Interrupts are disabled on entry as trap1 is an interrupt gate and they > >> * remain disabled throughout this function. > >> */ > >> -static int __kprobes post_kprobe_handler(struct pt_reg

Re: [PATCH -tip v8 08/26] kprobes/x86: Call exception handlers directly from do_int3/do_debug

2014-03-24 Thread Masami Hiramatsu
(2014/03/22 10:05), Steven Rostedt wrote: > On Wed, 05 Mar 2014 20:59:39 +0900 > Masami Hiramatsu wrote: > >> To avoid a kernel crash by probing on lockdep code, call >> kprobe_int3_handler and kprobe_debug_handler directly >> from do_int3 and do_debug. Since there is a locking code >> in notify_

Re: [PATCH -tip v8 08/26] kprobes/x86: Call exception handlers directly from do_int3/do_debug

2014-03-21 Thread Steven Rostedt
On Wed, 05 Mar 2014 20:59:39 +0900 Masami Hiramatsu wrote: > To avoid a kernel crash by probing on lockdep code, call > kprobe_int3_handler and kprobe_debug_handler directly > from do_int3 and do_debug. Since there is a locking code > in notify_die, lockdep code can be invoked. And because > the

[PATCH -tip v8 08/26] kprobes/x86: Call exception handlers directly from do_int3/do_debug

2014-03-05 Thread Masami Hiramatsu
To avoid a kernel crash by probing on lockdep code, call kprobe_int3_handler and kprobe_debug_handler directly from do_int3 and do_debug. Since there is a locking code in notify_die, lockdep code can be invoked. And because the lockdep involves printk() related things, theoretically, we need to pro