From: Peter Zijlstra <peterz@infradead.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: fuzzer causes lockup in x86_pmu_event_init()
Date: Tue, 17 Mar 2015 15:11:18 +0100 [thread overview]
Message-ID: <20150317141118.GD23123@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150317135536.GA14587@krava.brq.redhat.com>
On Tue, Mar 17, 2015 at 02:55:36PM +0100, Jiri Olsa wrote:
> On Mon, Mar 02, 2015 at 02:13:25PM -0500, Vince Weaver wrote:
> > On Sat, 28 Feb 2015, Jiri Olsa wrote:
> >
> > > hum, I dont see the locking is a problem.. but looks like once
> > > the sibling becomes singleton event, we dont init its sibling_list
> > >
> > > how about patch below.. compile tested ;-)
> >
> > so this is instead of PeterZ's patch?
> >
> > I'll start my test-machine fuzzing with this plus the infinite-interrupt
> > fix and see what happens. The machines do eventually trigger the issue
> > somwhat consistently but it can take up to a week before they hit it
> > so it's a tough one to test for.
>
> I guess no news is good news in here.. ;-)
>
> Peter, should I repost formal patch or you'll take it somehow
Yeah, please send with a proper changelog, I'll stuff it in someplace.
next prev parent reply other threads:[~2015-03-17 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 16:17 perf: fuzzer causes lockup in x86_pmu_event_init() Vince Weaver
2015-02-24 3:56 ` Vince Weaver
2015-02-25 15:16 ` Peter Zijlstra
2015-02-28 12:14 ` Jiri Olsa
2015-03-02 19:13 ` Vince Weaver
2015-03-04 10:32 ` Jiri Olsa
2015-03-17 13:55 ` Jiri Olsa
2015-03-17 14:11 ` Peter Zijlstra [this message]
2015-03-17 15:00 ` Vince Weaver
2015-03-17 14:10 ` Peter Zijlstra
2015-03-27 11:46 ` [tip:perf/core] perf: Fix racy group access tip-bot for Peter Zijlstra
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=20150317141118.GD23123@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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 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.