[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 7 Aug 2013 22:03:42 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Stephen Boyd <sboyd@...eaurora.org>
cc: Will Deacon <will.deacon@....com>,
Vince Weaver <vincent.weaver@...ne.edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Rutland <Mark.Rutland@....com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...hat.com>,
Paul Mackerras <paulus@...ba.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
"trinity@...r.kernel.org" <trinity@...r.kernel.org>
Subject: Re: perf,arm -- another (different) fuzzer oops
On Wed, 7 Aug 2013, Stephen Boyd wrote:
> Is config some really big value? It looks like config (or more
> specifically event->attr.config) is ecececec which is larger than 9
> (PERF_COUNT_HW_MAX). I'm fairly certain r4 is event->attr.type
> (PERF_TYPE_HARDWARE) and so we're out of bounds on that array access in
> armpmu_map_hw_event(). Does the below patch fix that?
Yes, it was big values in attr.config. I managed to bisect down to a
simple test case, which is attached. Oddly the test case has two events
before the oops happens; I should double check to make sure both are
really necessary.
I'll try this patch and see if it fixes things, thanks.
Vince
View attachment "arm_perf_new_oops.c" of type "TEXT/x-csrc" (2138 bytes)
Powered by blists - more mailing lists