From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
trinity@vger.kernel.org
Subject: Re: WARNING in arch/x86/kernel/cpu/perf_event.c
Date: Thu, 23 May 2013 17:26:57 +0200 [thread overview]
Message-ID: <20130523152657.GF23650@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1305231023240.17701@vincent-weaver-1.um.maine.edu>
On Thu, May 23, 2013 at 10:29:07AM -0400, Vince Weaver wrote:
> Hello,
>
> so now that I got past the OOPS in perf_mmap_close() I re-ran
> the fuzzer and quickly encountered the following WARNing.
>
> It happens here:
>
> static void x86_pmu_start(struct perf_event *event, int flags)
> {
> struct cpu_hw_events *cpuc = &__get_cpu_var(cpu_hw_events);
> int idx = event->hw.idx;
>
> if (WARN_ON_ONCE(!(event->hw.state & PERF_HES_STOPPED)))
> return;
>
>
> Is it worth trying to come up with a reproducible case for this one?
>
> I never know how seriously to take WARN_ON_ONCE dumps.
Its not supposed to happen, you're trying to start an already running
event. I'll put it on the todo list.
prev parent reply other threads:[~2013-05-23 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:29 Vince Weaver
2013-05-23 15:26 ` Peter Zijlstra [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=20130523152657.GF23650@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=trinity@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®