Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754643AbcJEIWY (ORCPT <rfc822;w@1wt.eu>);
        Wed, 5 Oct 2016 04:22:24 -0400
Received: from mx3-phx2.redhat.com ([209.132.183.24]:50063 "EHLO
        mx3-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752041AbcJEIWW (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 5 Oct 2016 04:22:22 -0400
Date: Wed, 5 Oct 2016 04:21:59 -0400 (EDT)
From: Jan Stancek <jstancek@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Jiri Olsa <jolsa@kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>,
        lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Michael Neuling <mikey@neuling.org>, Paul Mackerras <paulus@samba.org>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>
Message-ID: <283274720.499126.1475655719491.JavaMail.zimbra@redhat.com>
In-Reply-To: <87twcs4uys.fsf@concordia.ellerman.id.au>
References: <1474466134-21823-1-git-send-email-jolsa@kernel.org> <87twcs4uys.fsf@concordia.ellerman.id.au>
Subject: Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic
 context
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.34.26.57]
X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF38 (Linux)/8.0.6_GA_5922)
Thread-Topic: perf powerpc: Don't call perf_event_disable from atomic context
Thread-Index: WJKNMj+sBvSrkYkpSVf5oVuaEGFM0w==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1598
Lines: 39



----- Original Message -----
> From: "Michael Ellerman" <mpe@ellerman.id.au>
> To: "Jiri Olsa" <jolsa@kernel.org>, "Peter Zijlstra" <a.p.zijlstra@chello.nl>
> Cc: "lkml" <linux-kernel@vger.kernel.org>, "Ingo Molnar" <mingo@kernel.org>, "Michael Neuling" <mikey@neuling.org>,
> "Paul Mackerras" <paulus@samba.org>, "Alexander Shishkin" <alexander.shishkin@linux.intel.com>, "Jan Stancek"
> <jstancek@redhat.com>
> Sent: Tuesday, 4 October, 2016 6:08:27 AM
> Subject: Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context
> 
> Jiri Olsa <jolsa@kernel.org> 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?

As regular user:

# adduser dummy
# su dummy /mnt/testarea/trinity --children $proc_num -m --syslog -q -T DIE

Regards,
Jan