public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>
Subject: Re: perf: fuzzer triggers NULL pointer derefreence in x86_schedule_events
Date: Sun, 24 May 2015 21:14:19 +0200	[thread overview]
Message-ID: <20150524191419.GA5932@krava.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1504301448440.30050@vincent-weaver-1.umelst.maine.edu>

On Thu, Apr 30, 2015 at 03:08:56PM -0400, Vince Weaver wrote:
> 
> So the perf_fuzzer caught this after about a week of fuzzing on a Haswell 
> machine running a recent git kernel (pre 4.1-rc1 though).
> 
> We've seen this BUG before and various fixes were applied but apparently 
> it wasn't enough.
> 
> Sadly it doesn't seem to be reproducible.

hi,
did the trinity git tree change, I cant fetch it anymore...

[jolsa@krava trinity]$ git remote -v
origin  git://git.codemonkey.org.uk/trinity (fetch)
origin  git://git.codemonkey.org.uk/trinity (push)
[jolsa@krava trinity]$ git remote update
Fetching origin
fatal: Unable to look up git.codemonkey.org.uk (port 9418) (Name or service not known)
error: Could not fetch origin

thanks,
jirka

      parent reply	other threads:[~2015-05-24 19:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 19:08 perf: fuzzer triggers NULL pointer derefreence in x86_schedule_events Vince Weaver
2015-05-01 12:59 ` Peter Zijlstra
2015-05-04 19:32   ` Stephane Eranian
2015-05-07 12:43     ` Peter Zijlstra
2015-05-08  4:25       ` Vince Weaver
2015-05-18 17:40       ` Vince Weaver
2015-05-20 13:03         ` Peter Zijlstra
2015-05-20 13:15           ` Peter Zijlstra
2015-05-20 13:49           ` Peter Zijlstra
2015-05-20 15:26             ` Peter Zijlstra
2015-05-20 16:09               ` Peter Zijlstra
2015-05-24 19:14 ` Jiri Olsa [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=20150524191419.GA5932@krava.redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox