From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753544AbdKISLR (ORCPT ); Thu, 9 Nov 2017 13:11:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:51182 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751878AbdKISLP (ORCPT ); Thu, 9 Nov 2017 13:11:15 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BA1EA214EE Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Thu, 9 Nov 2017 13:11:11 -0500 From: Steven Rostedt To: Kaiwan N Billimoria Cc: Linus Torvalds , Laura Abbott , "Tobin C. Harding" , "kernel-hardening@lists.openwall.com" , "Jason A. Donenfeld" , "Theodore Ts'o" , Kees Cook , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Joe Perches , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon , Chris Fries , Dave Weinstein , Daniel Micay , Djalal Harouni , Linux Kernel Mailing List , Network Development , David Miller Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl Message-ID: <20171109131111.499057ab@gandalf.local.home> In-Reply-To: References: <1510050731-32446-1-git-send-email-me@tobin.cc> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 9 Nov 2017 10:24:32 +0530 Kaiwan N Billimoria wrote: > On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria > wrote: > >> But I don't know if there is anything else than the profiling code > >> that _really_ wants access to /proc/kallsyms in user space as a > >> regular user. > > > > Front-ends to ftrace, like trace-cmd? > [from the trace-cmd git repo (Steve Rostedt, pl stand up, pl stand up :-) > Documentation/trace-cmd-restore.1.txt : Yes, profiling and tracing are similar. And you need to be root to run the recording anyway. Thus, as long as root user can read kallsyms, trace-cmd should be fine. As trace-cmd requires root access to do any ftrace tracing. -- Steve From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl Date: Thu, 9 Nov 2017 13:11:11 -0500 Message-ID: <20171109131111.499057ab@gandalf.local.home> References: <1510050731-32446-1-git-send-email-me@tobin.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Laura Abbott , "Tobin C. Harding" , "kernel-hardening@lists.openwall.com" , "Jason A. Donenfeld" , "Theodore Ts'o" , Kees Cook , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Joe Perches , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, 9 Nov 2017 10:24:32 +0530 Kaiwan N Billimoria wrote: > On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria > wrote: > >> But I don't know if there is anything else than the profiling code > >> that _really_ wants access to /proc/kallsyms in user space as a > >> regular user. > > > > Front-ends to ftrace, like trace-cmd? > [from the trace-cmd git repo (Steve Rostedt, pl stand up, pl stand up :-) > Documentation/trace-cmd-restore.1.txt : Yes, profiling and tracing are similar. And you need to be root to run the recording anyway. Thus, as long as root user can read kallsyms, trace-cmd should be fine. As trace-cmd requires root access to do any ftrace tracing. -- Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 9 Nov 2017 13:11:11 -0500 From: Steven Rostedt Message-ID: <20171109131111.499057ab@gandalf.local.home> In-Reply-To: References: <1510050731-32446-1-git-send-email-me@tobin.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl To: Kaiwan N Billimoria Cc: Linus Torvalds , Laura Abbott , "Tobin C. Harding" , "kernel-hardening@lists.openwall.com" , "Jason A. Donenfeld" , Theodore Ts'o , Kees Cook , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Joe Perches , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon , Chris Fries , Dave Weinstein , Daniel Micay , Djalal Harouni , Linux Kernel Mailing List , Network Development , David Miller List-ID: On Thu, 9 Nov 2017 10:24:32 +0530 Kaiwan N Billimoria wrote: > On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria > wrote: > >> But I don't know if there is anything else than the profiling code > >> that _really_ wants access to /proc/kallsyms in user space as a > >> regular user. > > > > Front-ends to ftrace, like trace-cmd? > [from the trace-cmd git repo (Steve Rostedt, pl stand up, pl stand up :-) > Documentation/trace-cmd-restore.1.txt : Yes, profiling and tracing are similar. And you need to be root to run the recording anyway. Thus, as long as root user can read kallsyms, trace-cmd should be fine. As trace-cmd requires root access to do any ftrace tracing. -- Steve