public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: pi3orama@163.com, linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Zefan Li <lizefan@huawei.com>
Subject: Re: [PATCH 2/2] perf record: Fix crash when kptr is restricted
Date: Tue, 24 May 2016 09:41:26 -0300	[thread overview]
Message-ID: <20160524124126.GR8897@kernel.org> (raw)
In-Reply-To: <1464081688-167940-2-git-send-email-wangnan0@huawei.com>

Em Tue, May 24, 2016 at 09:21:28AM +0000, Wang Nan escreveu:
> Before this patch, a simple 'perf record' could fail if kptr_restrict
> is set to 1 (for normal user) or 2 (for root):
> 
>  # perf record ls
>  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)
> 
> This patch skips perf_event__synthesize_kernel_mmap() when kptr is not
> available.
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>

Thanks, applied and added a:

Fixes: 45e90056904b ("perf machine: Do not bail out if not managing to read ref reloc symbol")

But I'll investigate a bit more later, as the patch fixes the problem,
but I think probably it'd be better to check what is not being set up
in the ref reloc symbol stuff not bailed out by the patch above.

- Arnaldo

> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Zefan Li <lizefan@huawei.com>
> Cc: pi3orama@163.com
> ---
>  tools/perf/util/event.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
> index f6fcc68..9b141f1 100644
> --- a/tools/perf/util/event.c
> +++ b/tools/perf/util/event.c
> @@ -673,6 +673,8 @@ int perf_event__synthesize_kernel_mmap(struct perf_tool *tool,
>  	int err;
>  	union perf_event *event;
>  
> +	if (symbol_conf.kptr_restrict)
> +		return -1;
>  	if (map == NULL)
>  		return -1;
>  
> -- 
> 1.8.3.4

  parent reply	other threads:[~2016-05-24 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  9:21 [PATCH 1/2] perf tools: Check kptr_restrict for root Wang Nan
2016-05-24  9:21 ` [PATCH 2/2] perf record: Fix crash when kptr is restricted Wang Nan
2016-05-24 12:26   ` Arnaldo Carvalho de Melo
2016-05-24 12:41   ` Arnaldo Carvalho de Melo [this message]
2016-05-29 18:19   ` [tip:perf/urgent] " tip-bot for Wang Nan
2016-05-24 12:25 ` [PATCH 1/2] perf tools: Check kptr_restrict for root Arnaldo Carvalho de Melo
2016-05-29 18:19 ` [tip:perf/urgent] perf symbols: " tip-bot for Wang Nan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160524124126.GR8897@kernel.org \
    --to=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox