All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	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: Wed, 4 Mar 2015 11:32:31 +0100	[thread overview]
Message-ID: <20150304103231.GE16203@krava> (raw)
In-Reply-To: <alpine.DEB.2.11.1503021411020.17687@vincent-weaver-1.umelst.maine.edu>

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 think it's in addition.. Peter?

> 
> 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.

thanks,
jirka

  reply	other threads:[~2015-03-04 10:33 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 [this message]
2015-03-17 13:55         ` Jiri Olsa
2015-03-17 14:11           ` Peter Zijlstra
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=20150304103231.GE16203@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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.