From: Jiri Olsa <jolsa@redhat.com>
To: Song Shan Gong <gongss@linux.vnet.ibm.com>
Cc: acme@kernel.org, jolsa@kernel.org, dsahern@gmail.com,
linux-kernel@vger.kernel.org, borntraeger@de.ibm.com
Subject: Re: [RFC PATCH V2] s390/perf: fix 'start' address of module's map
Date: Mon, 18 Jul 2016 16:07:54 +0200 [thread overview]
Message-ID: <20160718140754.GA9555@krava> (raw)
In-Reply-To: <1468577711-6622-2-git-send-email-gongss@linux.vnet.ibm.com>
On Fri, Jul 15, 2016 at 06:15:11PM +0800, Song Shan Gong wrote:
> At preset, when creating module's map, perf gets 'start' address by parsing
> '/proc/modules', but it's module base address, isn't the start address of
> '.text' section. In most archs, it's OK. But for s390, it places 'GOT' and
> 'PLT' relocations before '.text' section. So there exists an offset between
> module base address and '.text' section, which will incur wrong symbol
> resolution for modules.
>
> Fix this bug by getting 'start' address of module's map from parsing
> '/sys/module/[module name]/sections/.text', not from '/proc/modules'.
>
> Signed-off-by: Song Shan Gong <gongss@linux.vnet.ibm.com>
> ---
> tools/perf/arch/s390/util/Build | 2 ++
> tools/perf/arch/s390/util/sym-handling.c | 27 +++++++++++++++++++++++++++
> tools/perf/util/machine.c | 8 ++++++++
> tools/perf/util/machine.h | 1 +
> 4 files changed, 38 insertions(+)
> create mode 100644 tools/perf/arch/s390/util/sym-handling.c
>
> diff --git a/tools/perf/arch/s390/util/Build b/tools/perf/arch/s390/util/Build
> index 8a61372..5e322ed 100644
> --- a/tools/perf/arch/s390/util/Build
> +++ b/tools/perf/arch/s390/util/Build
> @@ -2,3 +2,5 @@ libperf-y += header.o
> libperf-y += kvm-stat.o
>
> libperf-$(CONFIG_DWARF) += dwarf-regs.o
> +
> +libperf-y += sym-handling.o
> diff --git a/tools/perf/arch/s390/util/sym-handling.c b/tools/perf/arch/s390/util/sym-handling.c
> new file mode 100644
> index 0000000..ff51336
> --- /dev/null
> +++ b/tools/perf/arch/s390/util/sym-handling.c
> @@ -0,0 +1,27 @@
> +#include <stdio.h>
> +#include <stdlib.h>
> +#include <unistd.h>
> +#include "util.h"
> +#include "machine.h"
> +#include "api/fs/fs.h"
> +
> +int arch__fix_module_text_start(u64 *start, const char *name)
> +{
> + char path[PATH_MAX];
> + char *module_name = NULL;
> + int len;
> +
> + if (!(module_name = strdup(name)))
> + return -1;
> +
> + len = strlen(module_name);
> + module_name[len - 1] = '\0';
> + snprintf(path, PATH_MAX, "module/%s/sections/.text",
> + module_name + 1);
why can't you use 'name' in here? I can't see the reason
you allocated module_name..
> +
> + if (sysfs__read_ull(path, (unsigned long long *)start) < 0) {
> + free(module_name);
> + return -1;
> + }
leaking module_name in here
> + return 0;
> +}
SNIP
thanks,
jirka
next prev parent reply other threads:[~2016-07-18 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 10:15 [RFC PATCH V2]s390/perf:fix 'start' address of module's map Song Shan Gong
2016-07-15 10:15 ` [RFC PATCH V2] s390/perf: fix " Song Shan Gong
2016-07-18 1:52 ` Songshan Gong
2016-07-18 14:07 ` Jiri Olsa [this message]
[not found] ` <d32bfb65-a998-ebec-6dbf-348c4dd32149@linux.vnet.ibm.com>
2016-07-19 1:50 ` Songshan Gong
2016-07-19 3:35 ` Songshan Gong
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=20160718140754.GA9555@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=dsahern@gmail.com \
--cc=gongss@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox