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>
Subject: Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context
Date: Wed, 5 Oct 2016 04:21:59 -0400 (EDT) [thread overview]
Message-ID: <283274720.499126.1475655719491.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <87twcs4uys.fsf@concordia.ellerman.id.au>
----- 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
prev parent reply other threads:[~2016-10-05 8:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:55 [PATCH] perf powerpc: Don't call perf_event_disable from atomic context Jiri Olsa
2016-09-23 16:37 ` Peter Zijlstra
2016-10-03 13:29 ` Jiri Olsa
2016-10-03 13:47 ` Peter Zijlstra
2016-10-04 4:29 ` Michael Ellerman
2016-10-04 7:06 ` Peter Zijlstra
2016-10-10 13:19 ` Will Deacon
2016-10-05 8:09 ` Jiri Olsa
2016-10-05 19:53 ` Jiri Olsa
2016-10-06 7:24 ` Peter Zijlstra
2016-10-06 12:33 ` [PATCHv2] " Jiri Olsa
2016-10-24 12:26 ` Peter Zijlstra
2016-10-24 15:49 ` Jiri Olsa
2016-10-25 6:40 ` [perf powerpc] 18d1796d0b: [No primary change] kernel test robot
2016-10-25 6:40 ` [lkp] " kernel test robot
2016-10-25 9:06 ` Peter Zijlstra
2016-10-25 9:06 ` [lkp] " Peter Zijlstra
2016-10-26 2:09 ` Huang, Ying
2016-10-26 2:09 ` [LKP] [lkp] " Huang, Ying
2016-10-26 9:48 ` [PATCHv3] perf powerpc: Don't call perf_event_disable from atomic context Jiri Olsa
2016-10-26 9:48 ` Jiri Olsa
2016-10-26 15:12 ` Peter Zijlstra
2016-10-26 15:12 ` Peter Zijlstra
2016-10-26 15:24 ` Jiri Olsa
2016-10-26 15:24 ` Jiri Olsa
2016-10-28 10:10 ` [tip:perf/urgent] perf/powerpc: Don't call perf_event_disable() " tip-bot for Jiri Olsa
2016-10-04 4:08 ` [PATCH] perf powerpc: Don't call perf_event_disable " Michael Ellerman
2016-10-05 8:08 ` Jiri Olsa
2016-10-05 8:21 ` Jan Stancek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=283274720.499126.1475655719491.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikey@neuling.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.