All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: acme@ghostprotocols.net
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	peterz@infradead.org, eranian@google.com, namhyung.kim@lge.com
Subject: Re: [PATCH] perf report: fix crash showing warning related to kernel maps
Date: Sun, 15 Apr 2012 14:59:13 -0600	[thread overview]
Message-ID: <4F8B36A1.1090706@gmail.com> (raw)
In-Reply-To: <1334074526-67905-1-git-send-email-dsahern@gmail.com>

Hi Arnaldo:

Haven't seen this one come through your urgent queue.

On 4/10/12 10:15 AM, David Ahern wrote:
> While testing https://lkml.org/lkml/2012/4/10/123 I hit this crash:
>
> (gdb) bt
>   0  0x000000000042000f in __cmd_report (rep=0x7fff80cec580) at builtin-report.c:380
>   1  cmd_report (argc=0, argv=<optimized out>, prefix=<optimized out>) at builtin-report.c:759
>   2  0x0000000000414513 in run_builtin (p=0x7724a8, argc=3, argv=0x7fff80ceca70) at perf.c:273
>   3  0x0000000000413d41 in handle_internal_command (argv=0x7fff80ceca70, argc=3) at perf.c:345
>   4  run_argv (argv=0x7fff80cec880, argcp=0x7fff80cec88c) at perf.c:389
>   5  main (argc=3, argv=0x7fff80ceca70) at perf.c:487
>
> kernel_map can be NULL, so need to handle it while dumping a warning
> to user.
>
> Signed-off-by: David Ahern<dsahern@gmail.com>
> ---
>   tools/perf/builtin-report.c |   17 ++++++++++++-----
>   1 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> index 2e31743..002c644 100644
> --- a/tools/perf/builtin-report.c
> +++ b/tools/perf/builtin-report.c
> @@ -374,16 +374,23 @@ static int __cmd_report(struct perf_report *rep)
>   	    (kernel_map->dso->hit&&
>   	(kernel_kmap->ref_reloc_sym == NULL ||
>   	      kernel_kmap->ref_reloc_sym->addr == 0))) {
> -		const struct dso *kdso = kernel_map->dso;
> +		const char *desc =
> +		    "As no suitable kallsyms nor vmlinux was found, kernel samples\n"
> +		    "can't be resolved.";
> +
> +		if (kernel_map) {
> +			const struct dso *kdso = kernel_map->dso;
> +			if (RB_EMPTY_ROOT(&kdso->symbols[MAP__FUNCTION])) {
> +				desc = "If some relocation was applied (e.g. "
> +				       "kexec) symbols may be misresolved.";
> +			}
> +		}
>
>   		ui__warning(
>   "Kernel address maps (/proc/{kallsyms,modules}) were restricted.\n\n"
>   "Check /proc/sys/kernel/kptr_restrict before running 'perf record'.\n\n%s\n\n"
>   "Samples in kernel modules can't be resolved as well.\n\n",
> -			    RB_EMPTY_ROOT(&kdso->symbols[MAP__FUNCTION]) ?
> -"As no suitable kallsyms nor vmlinux was found, kernel samples\n"
> -"can't be resolved." :
> -"If some relocation was applied (e.g. kexec) symbols may be misresolved.");
> +		desc);
>   	}
>
>   	if (dump_trace) {


  reply	other threads:[~2012-04-15 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 16:15 [PATCH] perf report: fix crash showing warning related to kernel maps David Ahern
2012-04-15 20:59 ` David Ahern [this message]
2012-04-16  2:54 David Ahern

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=4F8B36A1.1090706@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --cc=peterz@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.