From: Irsa Lobard <www.upl.com@googlemail.com>
To: linux-numa@vger.kernel.org
Subject: memleak with node_cpu_mask_v2;
Date: Tue, 12 Aug 2014 10:08:39 +0200 [thread overview]
Message-ID: <CAM44gSwU2Mg9QTuMyPbhGJ_N_LTszLGAMCqHQSxMFJYGhOaAJw@mail.gmail.com> (raw)
Hello,
if I'm not mistaken, there is a memleak in numa_node_to_cpus_v2():
==8083== at 0x4C29DB4: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==8083== by 0x9AD0F8: init_node_cpu_mask_v2 (in)
==8083== by 0x9AD598: numa_node_to_cpus@@libnuma_1.2 (in)
==8083== by 0x42920B: get_cpu_mask_for_nodes (main.c)
Who will fix it?
Thanks
next reply other threads:[~2014-08-12 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 8:08 Irsa Lobard [this message]
2014-08-12 8:15 ` Fwd: memleak with node_cpu_mask_v2; Irsa Lobard
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=CAM44gSwU2Mg9QTuMyPbhGJ_N_LTszLGAMCqHQSxMFJYGhOaAJw@mail.gmail.com \
--to=www.upl.com@googlemail.com \
--cc=linux-numa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).