[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1902011125290.25915@macbook-air>
Date: Fri, 1 Feb 2019 11:27:28 -0500 (EST)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Jiri Olsa <jolsa@...hat.com>
cc: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>,
lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-perf-users@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Andi Kleen <ak@...ux.intel.com>, eranian@...gle.com,
vincent.weaver@...ne.edu,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
Subject: Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3)
On Fri, 1 Feb 2019, Jiri Olsa wrote:
> with attached patch I did not trigger the fuzzer crash
> for over a day now, could you guys try?
I've just started fuzzing with the patch applied. Often it takes a few
hours to trigger the bug.
Added question about this bug. It appeared that the crash was triggered
by the BTS driver over-writing kernel memory. The data being written, was
this user controllable? Meaning, is this a security issue being fixed, or
just a crashing issue?
Vince Weaver
vincent.weaver@...ne.edu
Powered by blists - more mailing lists