[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eg4ukc5f.fsf@ashishki-desk.ger.corp.intel.com>
Date: Thu, 08 Sep 2016 11:51:08 +0300
From: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To: Vince Weaver <vincent.weaver@...ne.edu>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
eranian@...gle.com, Arnaldo Carvalho de Melo <acme@...radead.org>,
vincent.weaver@...ne.edu
Subject: Re: [PATCH v2 0/5] perf, bts: Fallout from the fuzzer for perf/urgent
Vince Weaver <vincent.weaver@...ne.edu> writes:
> On the skylake machine with the original 5 patches I got this after
> continuing to fuzz. Sorry about the lack of frame pointer, next
> compile will have it enabled.
>
> If it matters, prior to this I hit the unrelated
> [25510.278199] WARNING: CPU: 1 PID: 25405 at kernel/events/core.c:3554 perf_event_read+0x18f/0x1a0
>
>
> [28682.174684] WARNING: CPU: 7 PID: 31992 at kernel/events/core.c:4961 perf_mmap_close+0x2e1/0x2f0
It just keeps on giving, doesn't it. I've got the same thing here during
the night, looking at it again. Did you capture the seed by any chance?
Thanks,
--
Alex
Powered by blists - more mailing lists