From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932573AbcEXM0H (ORCPT ); Tue, 24 May 2016 08:26:07 -0400 Received: from mail.kernel.org ([198.145.29.136]:35596 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752175AbcEXM0E (ORCPT ); Tue, 24 May 2016 08:26:04 -0400 Date: Tue, 24 May 2016 09:25:59 -0300 From: Arnaldo Carvalho de Melo To: Wang Nan Cc: pi3orama@163.com, linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo , Zefan Li Subject: Re: [PATCH 1/2] perf tools: Check kptr_restrict for root Message-ID: <20160524122559.GP8897@kernel.org> References: <1464081688-167940-1-git-send-email-wangnan0@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1464081688-167940-1-git-send-email-wangnan0@huawei.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Tue, May 24, 2016 at 09:21:27AM +0000, Wang Nan escreveu: > If kptr_restrict is set to 2, even root is not allowed to see pointers. > This patch checks kptr_restrict even if euid == 0. For root, report > error if kptr_restrict is 2. Improves the situation, but kptr_restrict=2 still causes a segfault: [root@jouet ~]# echo 2 > /proc/sys/kernel/kptr_restrict [root@jouet ~]# perf record usleep 1 Segmentation fault (core dumped) [root@jouet ~]# echo 1 > /proc/sys/kernel/kptr_restrict [root@jouet ~]# perf record usleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.018 MB perf.data (8 samples) ] [root@jouet ~]# echo 2 > /proc/sys/kernel/kptr_restrict [root@jouet ~]# perf record usleep 1 WARNING: Kernel address maps (/proc/{kallsyms,modules}) are restricted, check /proc/sys/kernel/kptr_restrict. Samples in kernel functions may not be resolved if a suitable vmlinux file is not found in the buildid cache or in the vmlinux path. Samples in kernel modules won't be resolved at all. If some relocation was applied (e.g. kexec) symbols may be misresolved even with a suitable vmlinux or kallsyms file. Segmentation fault (core dumped) [root@jouet ~]# Applying your patch and then investigating this other one. Thanks, - Arnaldo > Signed-off-by: Wang Nan > Cc: Arnaldo Carvalho de Melo > Cc: Zefan Li > Cc: pi3orama@163.com > --- > tools/perf/util/symbol.c | 16 ++++++++-------- > 1 file changed, 8 insertions(+), 8 deletions(-) > > diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c > index 20f9cb3..54c4ff2 100644 > --- a/tools/perf/util/symbol.c > +++ b/tools/perf/util/symbol.c > @@ -1933,17 +1933,17 @@ int setup_intlist(struct intlist **list, const char *list_str, > static bool symbol__read_kptr_restrict(void) > { > bool value = false; > + FILE *fp = fopen("/proc/sys/kernel/kptr_restrict", "r"); > > - if (geteuid() != 0) { > - FILE *fp = fopen("/proc/sys/kernel/kptr_restrict", "r"); > - if (fp != NULL) { > - char line[8]; > + if (fp != NULL) { > + char line[8]; > > - if (fgets(line, sizeof(line), fp) != NULL) > - value = atoi(line) != 0; > + if (fgets(line, sizeof(line), fp) != NULL) > + value = (geteuid() != 0) ? > + (atoi(line) != 0) : > + (atoi(line) == 2); > > - fclose(fp); > - } > + fclose(fp); > } > > return value; > -- > 1.8.3.4