public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Li Zhang <zhlcindy@linux.vnet.ibm.com>
Cc: acme@kernel.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] perf tools: Check access permission when reading /proc/kcore file.
Date: Tue, 16 Jun 2015 23:09:46 -0700	[thread overview]
Message-ID: <20150617060946.GA18162@us.ibm.com> (raw)
In-Reply-To: <1434350500-32342-1-git-send-email-zhlcindy@linux.vnet.ibm.com>

Li Zhang [zhlcindy@linux.vnet.ibm.com] wrote:
| When using command perf report --kallsyms=/proc/kallsyms with a non-root
| user, symbols are resolved. Then select one symbol and annotate it, it
| reports the error as the following:
| Can't annotate __clear_user: No vmlinux file with build id xxx was
| found.
| 
| The problem is caused by reading /proc/kcore without access permission.
| It needs to change access permission to allow a specific user to read
| /proc/kcore or use root to execute the perf command.
| 
| This patch is to check access permission when reading kcore file.
| 
| Signed-off-by: Li Zhang <zhlcindy@linux.vnet.ibm.com>
| ---
|  v2 -> v1:
|     * Report one useful message to users about the access permision,
|       then go back to the tools. Suggested by Arnaldo Carvalho de Melo.
| 
|  tools/perf/util/symbol.c | 4 ++++
|  1 file changed, 4 insertions(+)
| 
| diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
| index 201f6c4c..1bcd8dc 100644
| --- a/tools/perf/util/symbol.c
| +++ b/tools/perf/util/symbol.c
| @@ -1125,6 +1125,10 @@ static int dso__load_kcore(struct dso *dso, struct map *map,
|  	md.type = map->type;
|  	INIT_LIST_HEAD(&md.maps);
| 
| +	if (access(kcore_filename, R_OK))
| +		ui__warning("Insufficient permission to access %s.\n",
| +			    kcore_filename);
| +

Couple of comments. 

For consistency with rest of the file, use pr_warning() or pr_err(). 

Also, we could drop the access() call and report the error when open()
fails below?

|  	fd = open(kcore_filename, O_RDONLY);
|  	if (fd < 0)
|  		return -EINVAL;

Further, if user specifies the file with --kallsyms and we are not
able to read it, we should treat it as a fatal error and exit - this
would be easer when parsing command line args.

If user did not specify the option and we are proactively trying to
use /proc/kcore, we should not treat errors as fatal? i.e report
a warning message and continue without symbols?

| -- 
| 2.1.0


       reply	other threads:[~2015-06-17  6:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1434350500-32342-1-git-send-email-zhlcindy@linux.vnet.ibm.com>
2015-06-17  6:09 ` Sukadev Bhattiprolu [this message]
2015-06-18  3:31   ` [PATCH v2 1/1] perf tools: Check access permission when reading /proc/kcore file Li Zhang
2015-06-18  5:56     ` Sukadev Bhattiprolu
2015-06-18  8:24       ` Li Zhang

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=20150617060946.GA18162@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=zhlcindy@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox