From: Ingo Molnar <mingo@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Vince Weaver <vince@deater.net>,
"Yan, Zheng" <zheng.z.yan@intel.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCHSET/RFC 0/2] perf: Fix issues reported by perf fuzzer
Date: Thu, 11 Dec 2014 11:26:22 +0100 [thread overview]
Message-ID: <20141211102622.GA7997@gmail.com> (raw)
In-Reply-To: <1418243031-20367-1-git-send-email-jolsa@kernel.org>
* Jiri Olsa <jolsa@kernel.org> wrote:
> hi,
> Vince reported several issues with perf code hit by perf fuzzer,
> in here:
> http://marc.info/?l=linux-kernel&m=141806390822670&w=2
>
> I run the fuzzer, but wasn't able to hit issues reported
> by Vince. But.. I was lucky enough to hit other 2 issues
> described in following patches ;-)
>
> As I dont follow the uncore code much, it is sort of RFC
> patchset. However I'm running the fuzzer now for several
> hours and can't hit any other issue.
The changes are looking good to me so I've applied them to
tip:perf/urgent to give them more testing.
If they break anything in the uncore code's expectations the
uncore people should chime in. In any case, stability comes
first.
Thanks,
Ingo
prev parent reply other threads:[~2014-12-11 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 20:23 [PATCHSET/RFC 0/2] perf: Fix issues reported by perf fuzzer Jiri Olsa
2014-12-10 20:23 ` [PATCH 1/2] perf/x86/intel/uncore: Make sure only uncore events are collected Jiri Olsa
2014-12-10 23:51 ` Andi Kleen
2014-12-11 12:25 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2014-12-10 20:23 ` [PATCH 2/2] perf: Fix events installation during moving group Jiri Olsa
2014-12-11 12:25 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2014-12-11 10:26 ` Ingo Molnar [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=20141211102622.GA7997@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=vince@deater.net \
--cc=zheng.z.yan@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).