From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751423Ab3LLEkf (ORCPT ); Wed, 11 Dec 2013 23:40:35 -0500 Received: from mail7.hitachi.co.jp ([133.145.228.42]:34006 "EHLO mail7.hitachi.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751086Ab3LLEke (ORCPT ); Wed, 11 Dec 2013 23:40:34 -0500 Message-ID: <52A93E3A.9080600@hitachi.com> Date: Thu, 12 Dec 2013 13:40:26 +0900 From: Masami Hiramatsu Organization: Hitachi, Ltd., Japan User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Jiri Kosina Cc: Steven Rostedt , Ingo Molnar , Andi Kleen , Ananth N Mavinakayanahalli , Sandeepa Prabhu , Frederic Weisbecker , x86@kernel.org, lkml , Andrew Morton , Ingo Molnar , systemtap@sourceware.org, "H. Peter Anvin" , Sasha Levin , Thomas Gleixner , Seiji Aguchi , "David S. Miller" Subject: Re: [PATCH -tip v4 6/6] [RFC] kprobes/x86: Call exception handlers directly from do_int3/do_debug References: <20131204012841.22118.82992.stgit@kbuild-fedora.novalocal> <20131204012856.22118.91079.stgit@kbuild-fedora.novalocal> <20131203213904.5ff1794c@gandalf.local.home> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (2013/12/11 22:31), Jiri Kosina wrote: > On Tue, 3 Dec 2013, Steven Rostedt 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 ;-) > > Yeah, it's broken. Obviously, if you happen to trigger int3 before the > notifier has been registered, it'd cause int3 exception to be unhandled. > See > > commit 17f41571bb2c4a398785452ac2718a6c5d77180e > Author: Jiri Kosina > Date: Tue Jul 23 10:09:28 2013 +0200 > > kprobes/x86: Call out into INT3 handler directly instead of using notifier > > for one such issue that happened with jump labels. > >> Hmm, if there's no users of the int3 notifier, should we just remove it? > > Hmm, there are still uprobes, right? Right, uprobes still use it, however, since it only handles user-space breakpoint, there is no problem. Thank you! -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt@hitachi.com