From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: mingo@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, hpa@zytor.com,
torvalds@linux-foundation.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf: Fix PERF_EVENT_IOC_PERIOD migration race
Date: Wed, 12 Aug 2015 19:07:16 +0200 [thread overview]
Message-ID: <20150812170716.GV16853@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1508120947360.24663@vincent-weaver-1.umelst.maine.edu>
On Wed, Aug 12, 2015 at 09:49:40AM -0400, Vince Weaver wrote:
> On Wed, 12 Aug 2015, tip-bot for Peter Zijlstra wrote:
>
> > Commit-ID: c7999c6f3fed9e383d3131474588f282ae6d56b9
> > Gitweb: http://git.kernel.org/tip/c7999c6f3fed9e383d3131474588f282ae6d56b9
> > Author: Peter Zijlstra <peterz@infradead.org>
> > AuthorDate: Tue, 4 Aug 2015 19:22:49 +0200
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Wed, 12 Aug 2015 11:37:22 +0200
> >
> > perf: Fix PERF_EVENT_IOC_PERIOD migration race
> >
> > I ran the perf fuzzer, which triggered some WARN()s which are due to
> > trying to stop/restart an event on the wrong CPU.
>
> Do you have a list of which WARNs this should fix? Just so I can
> update my bug tracker.
I think this triggered:
arch/x86/kernel/cpu/perf_event.c:x86_pmu_del()
if (WARN_ON_ONCE(i == cpuc->n_events)) /* called ->del() without ->add() ? */
Through perf_ioctl()->perf_event_period().
I didn't safe a copy of the exact backtrace.
prev parent reply other threads:[~2015-08-12 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-c7999c6f3fed9e383d3131474588f282ae6d56b9@git.kernel.org>
2015-08-12 13:49 ` Vince Weaver
2015-08-12 17:07 ` 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=20150812170716.GV16853@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome