On Wed, 04 Dec 2013 01:28:56 +0000 Masami Hiramatsu <[email protected]> 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 lockdep involves printk() related things, theoretically, > we need to prohibit probing on much more code... > > Anyway, most of the int3 handlers in the kernel are already > called from do_int3 directly, e.g. ftrace_int3_handler, > poke_int3_handler, kgdb_ll_trap. Actually only > kprobe_exceptions_notify is on the notifier_call_chain. > > So I think this is not a crazy thing. What? Oh, yeah. No, using notifiers in int3 handler is the crazy thing ;-) Hmm, if there's no users of the int3 notifier, should we just remove it? -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
