[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160804155523.GO6879@twins.programming.kicks-ass.net>
Date: Thu, 4 Aug 2016 17:55:23 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Daniel Micay <danielmicay@...il.com>
Cc: kernel-hardening@...ts.openwall.com, Kees Cook <keescook@...omium.org>,
Jeff Vander Stoep <jeffv@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: Re: [PATCH 1/2] security, perf: allow further
restriction of perf_event_open
On Thu, Aug 04, 2016 at 11:44:28AM -0400, Daniel Micay wrote:
> This feature doesn't come from Android. The perf events subsystem in the
> mainline kernel is packed full of vulnerabilities too.
Uhh, not so much. I spend a _lot_ of time a while back to get the core
and x86 solid. I could run the fuzzers for hours on end at some point.
> The problem is so bad that pointing one of the public fuzzers at it
> for a short period of time is all that's required to start finding
> them.
If you know of any that reproduce on x86 I'll go fix. For anything else
you need to complain elsewhere as I don't have hardware nor bandwidth.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
