linux-kernel - Re: [QUERY] Why does perf-trace need me to be root?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131003062505.GE25345@gmail.com>
Date:	Thu, 3 Oct 2013 08:25:05 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Ramkumar Ramachandra <artagnon@...il.com>
Cc:	David Ahern <dsahern@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [QUERY] Why does perf-trace need me to be root?


* Ramkumar Ramachandra <artagnon@...il.com> wrote:

> David Ahern wrote:
> > If you trust your users make the debugfs mount point rx by group,world.
> 
> Thanks David. I can preserve this configuration across reboots by
> putting an entry in fstab, right? How do I preserve the value of
> /proc/sys/kernel/perf_event_paranoid across reboots?

via:

   echo 'kernel.perf_event_paranoid = -1' >> /etc/sysctl.conf

I think 'perf trace' should probably print such suggestions when it 
notices a privilege problem, to make it far more obvious for new users to 
correctly configure their system for easy tracing.

The current output:

  comet:~/tip> perf trace
  Couldn't read the raw_syscalls tracepoints information!

is as hostile to the user as it gets ;-)

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/