Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752692Ab3GHRrM (ORCPT ); Mon, 8 Jul 2013 13:47:12 -0400 Received: from merlin.infradead.org ([205.233.59.134]:39188 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752057Ab3GHRrL (ORCPT ); Mon, 8 Jul 2013 13:47:11 -0400 Date: Mon, 8 Jul 2013 19:46:22 +0200 From: Peter Zijlstra To: Jiri Olsa Cc: Vince Weaver , linux-kernel@vger.kernel.org, Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , trinity@vger.kernel.org Subject: Re: [bisected] perf: yet another fuzzer triggered crash Message-ID: <20130708174622.GA25631@dyad.programming.kicks-ass.net> References: <20130701090713.GO6626@twins.programming.kicks-ass.net> <20130703074929.GE23916@twins.programming.kicks-ass.net> <20130708135048.GA1069@krava.brq.redhat.com> <20130708165023.GD22923@dyad.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130708165023.GD22923@dyad.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2820 Lines: 46 On Mon, Jul 08, 2013 at 06:50:23PM +0200, Peter Zijlstra wrote: > > [ 324.983534] ------------[ cut here ]------------ > [ 324.984420] WARNING: at /usr/src/linux-2.6/kernel/events/core.c:1953 __perf_event_enable+0x187/0x190() > [ 324.984420] Modules linked in: > [ 324.984420] CPU: 19 PID: 2715 Comm: nmi_bug_snb Not tainted 3.10.0+ #246 > [ 324.984420] Hardware name: Supermicro X8DTN/X8DTN, BIOS 4.6.3 01/08/2010 > [ 324.984420] 0000000000000009 ffff88043fce3ec8 ffffffff8160ea0b ffff88043fce3f00 > [ 324.984420] ffffffff81080ff0 ffff8802314fdc00 ffff880231a8f800 ffff88043fcf7860 > [ 324.984420] 0000000000000286 ffff880231a8f800 ffff88043fce3f10 ffffffff8108103a > [ 324.984420] Call Trace: > [ 324.984420] [] dump_stack+0x19/0x1b > [ 324.984420] [] warn_slowpath_common+0x70/0xa0 > [ 324.984420] [] warn_slowpath_null+0x1a/0x20 > [ 324.984420] [] __perf_event_enable+0x187/0x190 > [ 324.984420] [] remote_function+0x40/0x50 > [ 324.984420] [] generic_smp_call_function_single_interrupt+0xbe/0x130 > [ 324.984420] [] smp_call_function_single_interrupt+0x27/0x40 > [ 324.984420] [] call_function_single_interrupt+0x6f/0x80 > [ 324.984420] [] ? _raw_spin_unlock_irqrestore+0x41/0x70 > [ 324.984420] [] perf_event_exit_task+0x14d/0x210 > [ 324.984420] [] ? switch_task_namespaces+0x24/0x60 > [ 324.984420] [] do_exit+0x2b6/0xa40 > [ 324.984420] [] ? _raw_spin_unlock_irq+0x2c/0x30 > [ 324.984420] [] do_group_exit+0x49/0xc0 > [ 324.984420] [] get_signal_to_deliver+0x254/0x620 > [ 324.984420] [] do_signal+0x57/0x5a0 > [ 324.984420] [] ? __do_page_fault+0x2a4/0x4e0 > [ 324.984420] [] ? retint_restore_args+0xe/0xe > [ 324.984420] [] ? retint_signal+0x11/0x84 > [ 324.984420] [] do_notify_resume+0x65/0x80 > [ 324.984420] [] retint_signal+0x46/0x84 > [ 324.984420] ---[ end trace 442ec2f04db3771a ]--- OK, this looks like an unrelated issue. Still wants fixing though. It looks like we get an IPI from perf_event_enable() right after we release child_ctx->lock in perf_event_exit_task_context(). I don't see what we could do here other than write a comment and remove the WARN. It seems a valid, albeit, unlikely scenario. -- 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/