Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752812AbcJDEIf (ORCPT ); Tue, 4 Oct 2016 00:08:35 -0400 Received: from ozlabs.org ([103.22.144.67]:42437 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752425AbcJDEI3 (ORCPT ); Tue, 4 Oct 2016 00:08:29 -0400 From: Michael Ellerman To: Jiri Olsa , Peter Zijlstra Cc: lkml , Ingo Molnar , Michael Neuling , Paul Mackerras , Alexander Shishkin , Jan Stancek Subject: Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context In-Reply-To: <1474466134-21823-1-git-send-email-jolsa@kernel.org> References: <1474466134-21823-1-git-send-email-jolsa@kernel.org> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Tue, 04 Oct 2016 15:08:27 +1100 Message-ID: <87twcs4uys.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 886 Lines: 20 Jiri Olsa writes: > The trinity syscall fuzzer triggered following WARN on powerpc: > WARNING: CPU: 9 PID: 2998 at arch/powerpc/kernel/hw_breakpoint.c:278 > ... > NIP [c00000000093aedc] .hw_breakpoint_handler+0x28c/0x2b0 > LR [c00000000093aed8] .hw_breakpoint_handler+0x288/0x2b0 > Call Trace: > [c0000002f7933580] [c00000000093aed8] .hw_breakpoint_handler+0x288/0x2b0 (unreliable) > [c0000002f7933630] [c0000000000f671c] .notifier_call_chain+0x7c/0xf0 > [c0000002f79336d0] [c0000000000f6abc] .__atomic_notifier_call_chain+0xbc/0x1c0 > [c0000002f7933780] [c0000000000f6c40] .notify_die+0x70/0xd0 > [c0000002f7933820] [c00000000001a74c] .do_break+0x4c/0x100 > [c0000002f7933920] [c0000000000089fc] handle_dabr_fault+0x14/0x48 Is that the full stack trace? It doesn't look like it. And were you running trinity as root or regular user? cheers