From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v3 1/3] perf annotate: Fix a bug reading link name from a build-id file
Date: Tue, 28 Mar 2017 20:54:28 +0900 [thread overview]
Message-ID: <456b6572-2a3e-c8d9-8272-391c21bdb596@gmail.com> (raw)
In-Reply-To: <20170327180140.GB27431@kernel.org>
On 03/28/2017 03:01 AM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 27, 2017 at 04:10:36PM +0900, Taeung Song escreveu:
>> It is wrong way to read link name from a build-id file.
>> Because a build-id file is not symbolic link
>> but build-id directory of it is symbolic link, so fix it.
>
> Ok, applied, in the past it was always a symlink, but the following cset
> changed that, so I added:
>
> Fixes: 01412261d994 ("perf buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid")
>
> Thanks,
>
> - Arnaldo
Thank you!
- Taeung
>
>> For example, if build-id file name gotten from
>> dso__build_id_filename() is as below,
>>
>> /root/.debug/.build-id/4f/75c7d197c951659d1c1b8b5fd49bcdf8f3f8b1/elf
>>
>> To correctly read link name of build-id,
>> use the build-id dir path that is a symbolic link,
>> instead of the above build-id file name like below.
>>
>> /root/.debug/.build-id/4f/75c7d197c951659d1c1b8b5fd49bcdf8f3f8b1
>>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Cc: Jiri Olsa <jolsa@redhat.com>
>> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
>> ---
>> tools/perf/util/annotate.c | 10 +++++++++-
>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
>> index 3d0263e..6dc9148 100644
>> --- a/tools/perf/util/annotate.c
>> +++ b/tools/perf/util/annotate.c
>> @@ -1307,6 +1307,7 @@ static int dso__disassemble_filename(struct dso *dso, char *filename, size_t fil
>> {
>> char linkname[PATH_MAX];
>> char *build_id_filename;
>> + char *build_id_path = NULL;
>>
>> if (dso->symtab_type == DSO_BINARY_TYPE__KALLSYMS &&
>> !dso__is_kcore(dso))
>> @@ -1322,8 +1323,14 @@ static int dso__disassemble_filename(struct dso *dso, char *filename, size_t fil
>> goto fallback;
>> }
>>
>> + build_id_path = strdup(filename);
>> + if (!build_id_path)
>> + return -1;
>> +
>> + dirname(build_id_path);
>> +
>> if (dso__is_kcore(dso) ||
>> - readlink(filename, linkname, sizeof(linkname)) < 0 ||
>> + readlink(build_id_path, linkname, sizeof(linkname)) < 0 ||
>> strstr(linkname, DSO__NAME_KALLSYMS) ||
>> access(filename, R_OK)) {
>> fallback:
>> @@ -1335,6 +1342,7 @@ static int dso__disassemble_filename(struct dso *dso, char *filename, size_t fil
>> __symbol__join_symfs(filename, filename_size, dso->long_name);
>> }
>>
>> + free(build_id_path);
>> return 0;
>> }
>>
>> --
>> 2.7.4
next prev parent reply other threads:[~2017-03-28 11:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 7:10 [PATCH v3 0/3] perf annotate: Simple bugfixes Taeung Song
2017-03-27 7:10 ` [PATCH v3 1/3] perf annotate: Fix a bug reading link name from a build-id file Taeung Song
2017-03-27 18:01 ` Arnaldo Carvalho de Melo
2017-03-28 11:54 ` Taeung Song [this message]
2017-03-28 5:55 ` [tip:perf/core] perf annotate: Fix a bug following symbolic link of " tip-bot for Taeung Song
2017-03-27 7:10 ` [PATCH v3 2/3] perf annotate: Fix a bug of division by zero when calculating percent Taeung Song
2017-03-28 5:55 ` [tip:perf/core] " tip-bot for Taeung Song
2017-03-27 7:10 ` [PATCH v3 3/3] perf annotate: Fix missing number of samples Taeung Song
2017-03-27 18:26 ` Arnaldo Carvalho de Melo
2017-03-28 12:09 ` Taeung Song
2017-03-28 14:38 ` Taeung Song
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=456b6572-2a3e-c8d9-8272-391c21bdb596@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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
Powered by JetHome