From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
Namhyung Kim <namhyung@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>, Minchan Kim <minchan@kernel.org>
Subject: [PATCH 2/2] perf tools: Check validity of --symfs value
Date: Fri, 25 Jul 2014 10:31:48 +0900 [thread overview]
Message-ID: <1406251908-8195-2-git-send-email-namhyung@kernel.org> (raw)
In-Reply-To: <1406251908-8195-1-git-send-email-namhyung@kernel.org>
If a symfs is given by user, it needs to be checked before applying.
Currently, it just uses it even if realpath() failed.
I guess it's because it needed to handle empty symfs which is the
default value. But now it's only called when it's not empty so it'd
be better to check before using it and warn users if failed.
Cc: Minchan Kim <minchan@kernel.org>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/perf/util/symbol.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/symbol.c b/tools/perf/util/symbol.c
index 90723a12e947..95186185c1d5 100644
--- a/tools/perf/util/symbol.c
+++ b/tools/perf/util/symbol.c
@@ -1864,8 +1864,11 @@ int symbol__init(void)
if (*symbol_conf.symfs) {
symfs = realpath(symbol_conf.symfs, NULL);
- if (symfs == NULL)
- symfs = (char *)symbol_conf.symfs;
+ if (symfs == NULL) {
+ pr_err("cannot apply symfs: %s: %s\n",
+ symbol_conf.symfs, strerror(errno));
+ return -1;
+ }
/*
* A path to symbols of "/" is identical to ""
--
2.0.0
next prev parent reply other threads:[~2014-07-25 1:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 1:31 [PATCH 1/2] perf tools: Ensure --symfs ends with '/' Namhyung Kim
2014-07-25 1:31 ` Namhyung Kim [this message]
2014-07-25 13:15 ` Arnaldo Carvalho de Melo
2014-07-28 1:04 ` Namhyung Kim
2014-07-29 5:02 ` Minchan Kim
2014-07-29 12:33 ` Arnaldo Carvalho de Melo
2014-07-29 13:26 ` Minchan Kim
2014-07-29 13:43 ` Arnaldo Carvalho de Melo
2014-07-29 15:12 ` Arnaldo Carvalho de Melo
2014-07-29 13:57 ` David Ahern
2014-07-29 23:52 ` Namhyung Kim
2014-07-30 15:19 ` Arnaldo Carvalho de Melo
2014-07-30 20:55 ` Arnaldo Carvalho de Melo
2014-07-30 22:20 ` David Ahern
2014-07-31 4:25 ` Namhyung Kim
2014-07-31 12:26 ` Arnaldo Carvalho de Melo
2014-07-31 23:38 ` Namhyung Kim
2014-08-01 20:15 ` Arnaldo Carvalho de Melo
2014-08-11 7:38 ` Namhyung Kim
2014-08-11 13:15 ` 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=1406251908-8195-2-git-send-email-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.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.