Skip to contentSkip to conversation

perf_counters: Increase paranoia level

tip:perfcounters/urgent tip-bot for Ingo Molnar 1 participant 1 message Aug 28, 2009

lore
Share & tools
lore
#0 lore raw
Commit-ID:  6bb56347f5162d1a7cb1dc461023360781ecd4c0
Gitweb:     http://git.kernel.org/tip/6bb56347f5162d1a7cb1dc461023360781ecd4c0
Author:     Ingo Molnar <[email protected]>
AuthorDate: Fri, 28 Aug 2009 13:44:53 +0200
Committer:  Ingo Molnar <[email protected]>
CommitDate: Fri, 28 Aug 2009 13:44:53 +0200

perf_counters: Increase paranoia level

Per-cpu counters are an ASLR information leak as they show the execution other tasks do. Increase the paranoia level to 1, which disallows per-cpu counters. (they still allow counting/profiling of own tasks - and admin can profile everything.)

Cc Mike Galbraith <[email protected]>
Cc Paul Mackerras <[email protected]>
Cc Arnaldo Carvalho de Melo <[email protected]>
Cc Frederic Weisbecker <[email protected]>

LKML-Reference: <new-submission>

---
 kernel/perf_counter.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
kernel/perf_counter.c +1 -1
index f274e19..7d4bb83 100644
@@ -50,7 +50,7 @@ static atomic_t nr_task_counters __read_mostly;
  *  1 - disallow cpu counters to unpriv
  *  2 - disallow kernel profiling to unpriv
  */
-int sysctl_perf_counter_paranoid __read_mostly;
+int sysctl_perf_counter_paranoid __read_mostly = 1;
 
 static inline bool perf_paranoid_cpu(void)
 {