From: Jiri Olsa <jolsa@redhat.com>
To: linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf: buildid-cache zero out buffer of filenames when adding/remoing buildid
Date: Mon, 18 Jul 2011 12:34:15 +0200 [thread overview]
Message-ID: <20110718103415.GA1978@jolsa.brq.redhat.com> (raw)
In-Reply-To: <20110718031314.GA5802@hpt.nay.redhat.com>
On Mon, Jul 18, 2011 at 11:13:14AM +0800, Han Pingtian wrote:
> readlink() doesn't append a null byte to buf. So we should zero out buf
> with zalloc(). Or we'll see sometimes error like this:
>
> [root@intel-s3e36-01]~# /usr/bin/perf buildid-cache -a /lib/modules/2.6.32-130.el6.x86_64/kernel/crypto/twofish_common.ko -v
> Adding f64ba8efd5f53c7ad332fc17db1d21de309038e1 /lib/modules/2.6.32-130.el6.x86_64/kernel/crypto/twofish_common.ko: Ok
> [root@intel-s3e36-01]~# /usr/bin/perf buildid-cache -r /lib/modules/2.6.32-130.el6.x86_64/kernel/crypto/twofish_common.ko -v
> Removing f64ba8efd5f53c7ad332fc17db1d21de309038e1 /lib/modules/2.6.32-130.el6.x86_64/kernel/crypto/twofish_common.ko: FAIL
> /lib/modules/2.6.32-130.el6.x86_64/kernel/crypto/twofish_common.ko wasn't in the cache
>
> The change in build_id_cache__add_s() is a defense.
>
> Signed-off-by: Han Pingtian <phan@redhat.com>
works for me
Tested-by: Jiri Olsa <jolsa@redhat.com>
> ---
> tools/perf/util/header.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index afb0849..36d723d 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -189,8 +189,8 @@ int build_id_cache__add_s(const char *sbuild_id, const char *debugdir,
> const char *name, bool is_kallsyms)
> {
> const size_t size = PATH_MAX;
> - char *realname, *filename = malloc(size),
> - *linkname = malloc(size), *targetname;
> + char *realname, *filename = zalloc(size),
> + *linkname = zalloc(size), *targetname;
> int len, err = -1;
>
> if (is_kallsyms) {
> @@ -254,8 +254,8 @@ static int build_id_cache__add_b(const u8 *build_id, size_t build_id_size,
> int build_id_cache__remove_s(const char *sbuild_id, const char *debugdir)
> {
> const size_t size = PATH_MAX;
> - char *filename = malloc(size),
> - *linkname = malloc(size);
> + char *filename = zalloc(size),
> + *linkname = zalloc(size);
> int err = -1;
>
> if (filename == NULL || linkname == NULL)
> --
> 1.7.1
next prev parent reply other threads:[~2011-07-18 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 3:13 Han Pingtian
2011-07-18 10:34 ` Jiri Olsa [this message]
2011-08-05 10:06 ` [tip:perf/urgent] perf buildid-cache: Zero out buffer of filenames when adding/removing buildid tip-bot for Han Pingtian
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=20110718103415.GA1978@jolsa.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--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
Powered by JetHome