All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org, aneesh.kumar@linux.ibm.com,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 1/2] perf/probe: Report possible permission error for map__load failure
Date: Fri, 4 Jun 2021 16:18:47 -0300	[thread overview]
Message-ID: <YLp8lxoSPmUtQUra@kernel.org> (raw)
In-Reply-To: <162282065877.448336.10047912688119745151.stgit@devnote2>

Em Sat, Jun 05, 2021 at 12:30:58AM +0900, Masami Hiramatsu escreveu:
> Report possible permission error including kptr_restrict setting
> for map__load() failure. This can happen when non-superuser runs
> perf probe.
> 
> With this patch, perf probe shows the following message.
> 
>  $ perf probe vfs_read
>  Failed to load symbols from /proc/kallsyms
>  Please ensure you can read the /proc/kallsyms symbol addresses.
>  If the /proc/sys/kernel/kptr_restrict is '2', you can not read
>  kernel symbol address even if you are a superuser. Please change
>  it to '1'. If kptr_restrict is '1', the superuser can read the
>  symbol addresses.
>  In that case, please run this command again with sudo.
>    Error: Failed to add events.

Thanks, applied.

- Arnaldo

 
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
>  tools/perf/util/probe-event.c |   25 ++++++++++++++++++++++---
>  1 file changed, 22 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 3a7649835ec9..8fe179d671c3 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -2936,7 +2936,7 @@ static int find_probe_functions(struct map *map, char *name,
>  	bool cut_version = true;
>  
>  	if (map__load(map) < 0)
> -		return 0;
> +		return -EACCES;	/* Possible permission error to load symbols */
>  
>  	/* If user gives a version, don't cut off the version from symbols */
>  	if (strchr(name, '@'))
> @@ -2975,6 +2975,17 @@ void __weak arch__fix_tev_from_maps(struct perf_probe_event *pev __maybe_unused,
>  				struct map *map __maybe_unused,
>  				struct symbol *sym __maybe_unused) { }
>  
> +
> +static void pr_kallsyms_access_error(void)
> +{
> +	pr_err("Please ensure you can read the /proc/kallsyms symbol addresses.\n"
> +	       "If the /proc/sys/kernel/kptr_restrict is '2', you can not read\n"
> +	       "kernel symbol address even if you are a superuser. Please change\n"
> +	       "it to '1'. If kptr_restrict is '1', the superuser can read the\n"
> +	       "symbol addresses.\n"
> +	       "In that case, please run this command again with sudo.\n");
> +}
> +
>  /*
>   * Find probe function addresses from map.
>   * Return an error or the number of found probe_trace_event
> @@ -3011,8 +3022,16 @@ static int find_probe_trace_events_from_map(struct perf_probe_event *pev,
>  	 */
>  	num_matched_functions = find_probe_functions(map, pp->function, syms);
>  	if (num_matched_functions <= 0) {
> -		pr_err("Failed to find symbol %s in %s\n", pp->function,
> -			pev->target ? : "kernel");
> +		if (num_matched_functions == -EACCES) {
> +			pr_err("Failed to load symbols from %s\n",
> +			       pev->target ?: "/proc/kallsyms");
> +			if (pev->target)
> +				pr_err("Please ensure the file is not stripped.\n");
> +			else
> +				pr_kallsyms_access_error();
> +		} else
> +			pr_err("Failed to find symbol %s in %s\n", pp->function,
> +				pev->target ? : "kernel");
>  		ret = -ENOENT;
>  		goto out;
>  	} else if (num_matched_functions > probe_conf.max_probes) {
> 

-- 

- Arnaldo

  reply	other threads:[~2021-06-04 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 15:30 [PATCH 0/2] perf probe: Report permission errors Masami Hiramatsu
2021-06-04 15:30 ` [PATCH 1/2] perf/probe: Report possible permission error for map__load failure Masami Hiramatsu
2021-06-04 19:18   ` Arnaldo Carvalho de Melo [this message]
2021-06-06  7:11     ` Namhyung Kim
2021-06-07  0:00       ` Masami Hiramatsu
2021-06-08 12:24         ` Arnaldo Carvalho de Melo
2021-06-04 15:31 ` [PATCH 2/2] perf/probe: Report permission error for tracefs error Masami Hiramatsu
2021-06-04 19:18   ` Arnaldo Carvalho de Melo
2021-06-05  3:56     ` Masami Hiramatsu
2021-06-06 15:49       ` [PATCH v2] perf/probe: Report permission error for tracefs access Masami Hiramatsu
2021-06-08 17:13         ` Arnaldo Carvalho de Melo

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=YLp8lxoSPmUtQUra@kernel.org \
    --to=acme@kernel.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.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 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.