From: Vince Weaver <vincent.weaver@maine.edu>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
eranian@google.com,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3)
Date: Sat, 2 Feb 2019 12:58:07 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1902021255370.5674@macbook-air> (raw)
In-Reply-To: <20190201173816.GA19907@krava>
On Fri, 1 Feb 2019, Jiri Olsa wrote:
> >
> > I've just started fuzzing with the patch applied. Often it takes a few
> > hours to trigger the bug.
>
> cool, thanks
I let it run overnight and no crash.
> > 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?
>
> yea, I have an example that can trigger it immediately
I mean: the crash is happening because data structures are getting
over-written by the BTS driver. Depending who and what is doing this,
this could be a security issue (i.e. if it was raw BTS data that was
partially userspace controlled values). Though even if this were the case
it would probably be hard to exploit.
Vince
next prev parent reply other threads:[~2019-02-02 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 6:46 Ravi Bangoria
2019-01-25 15:11 ` Vince Weaver
2019-01-25 16:00 ` Andi Kleen
2019-01-31 7:58 ` Ravi Bangoria
2019-01-31 13:00 ` Andi Kleen
2019-01-31 20:27 ` Cong Wang
2019-01-31 20:39 ` Andi Kleen
2019-03-06 23:09 ` Pavel Machek
2019-01-30 18:36 ` Jiri Olsa
2019-01-30 20:39 ` Andi Kleen
2019-01-30 22:33 ` Jiri Olsa
2019-01-31 7:36 ` Jiri Olsa
2019-01-31 8:27 ` Jiri Olsa
2019-02-01 7:43 ` Jiri Olsa
2019-02-01 7:54 ` Ravi Bangoria
2019-02-02 3:24 ` Ravi Bangoria
2019-02-02 10:34 ` Jiri Olsa
2019-02-01 16:27 ` Vince Weaver
2019-02-01 17:38 ` Jiri Olsa
2019-02-02 17:58 ` Vince Weaver [this message]
2019-02-04 12:35 ` [PATCH] perf: Add check_period pmu callback Jiri Olsa
2019-02-11 10:11 ` Peter Zijlstra
2019-02-11 13:22 ` [tip:perf/urgent] perf/x86: Add check_period PMU callback tip-bot for Jiri Olsa
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=alpine.DEB.2.21.1902021255370.5674@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.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
all inboxes | Powered by JetHome®