Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S944507AbcJSPLt (ORCPT ); Wed, 19 Oct 2016 11:11:49 -0400 Received: from mail.kernel.org ([198.145.29.136]:51494 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S944362AbcJSPLm (ORCPT ); Wed, 19 Oct 2016 11:11:42 -0400 Date: Wed, 19 Oct 2016 07:26:02 -0300 From: Arnaldo Carvalho de Melo To: Peter Zijlstra Cc: Daniel Micay , kernel-hardening@lists.openwall.com, Mark Rutland , Ingo Molnar , Alexander Shishkin , "linux-doc@vger.kernel.org" , LKML , Jeff Vander Stoep Subject: Re: [kernel-hardening] [PATCH 1/2] security, perf: allow further restriction of perf_event_open Message-ID: <20161019102602.GA25522@kernel.org> References: <1469630746-32279-1-git-send-email-jeffv@google.com> <20161017134413.GK29095@leverpostej> <1476825301.4032.7.camel@gmail.com> <20161019100126.GI3102@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161019100126.GI3102@twins.programming.kicks-ass.net> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1343 Lines: 30 Em Wed, Oct 19, 2016 at 12:01:26PM +0200, Peter Zijlstra escreveu: > On Tue, Oct 18, 2016 at 05:15:01PM -0400, Daniel Micay wrote: > > It's also worth noting that fine-grained control via a scoped mechanism > > would likely only be used to implement *more restrictions* on Android, > > not to make the feature less aggressive. > > It's desirable for perf events to be disabled by default for non-root > > across the board on Android. > Right, but this is Android. The knob seems to now also live in Debian > (and derived) distros. And there it is utter crap. > It completely defeats having perf for a fairly large segment of > corporate developers who do not get to have root on their own machines > (which is stupid policy but whatever). > It similarly defeats development of self profiling JITs and whatnot. > A capability would allow people to run perf (or another sanctioned > binary), even though in general they cannot do sys_perf_event_open(). But self profiling JITs would be useful for non-developers, on Android (anywhere, really), and for that it would require being able to at least, well, self profile, using sys_perf_event_open() by a normal process, limited to profiling itself, no? This not being possible, self profiling will use some other means, its like sys_perf_event_open() never existed for them. - Arnaldo