From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sohaib Mohamed <sohaib.amhmd@gmail.com>
Cc: irogers@google.com, linux-perf-users@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf_counter tools: Fix memory leaks of add_cmdname()
Date: Thu, 25 Nov 2021 18:38:46 -0300 [thread overview]
Message-ID: <YaACZsT6pupginXC@kernel.org> (raw)
In-Reply-To: <20211119084637.178890-1-sohaib.amhmd@gmail.com>
Em Fri, Nov 19, 2021 at 10:46:36AM +0200, Sohaib Mohamed escreveu:
> ASan reports some memory leaks when running:
>
> $ perf xyz
>
> This patch adds the missing clean_cmdnames()
>
> Fixes: 078006012401 ("perf_counter tools: add in basic glue from Git")
>
> Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
> ---
> tools/lib/subcmd/help.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/lib/subcmd/help.c b/tools/lib/subcmd/help.c
> index bf02d62a3b2b..4a433f4d19a1 100644
> --- a/tools/lib/subcmd/help.c
> +++ b/tools/lib/subcmd/help.c
> @@ -187,6 +187,7 @@ static void list_commands_in_dir(struct cmdnames *cmds,
>
> add_cmdname(cmds, de->d_name + prefix_len, entlen);
> }
> + clean_cmdnames(cmds);
Have you tested this?
Look at this usage:
void load_command_list(const char *prefix,
struct cmdnames *main_cmds,
struct cmdnames *other_cmds)
{
const char *env_path = getenv("PATH");
char *exec_path = get_argv_exec_path();
if (exec_path) {
list_commands_in_dir(main_cmds, exec_path, prefix);
qsort(main_cmds->names, main_cmds->cnt,
sizeof(*main_cmds->names), cmdname_compare);
uniq(main_cmds);
}
If you call clean_cmdnames() in list_commands_in_dir() that call to
qsort will be with main_cmds emptied, no?
- Arnaldo
> closedir(dir);
> free(buf);
> }
> --
> 2.25.1
--
- Arnaldo
prev parent reply other threads:[~2021-11-25 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 8:46 [PATCH] perf_counter tools: Fix memory leaks of add_cmdname() Sohaib Mohamed
2021-11-25 21:38 ` Arnaldo Carvalho de Melo [this message]
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=YaACZsT6pupginXC@kernel.org \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sohaib.amhmd@gmail.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;
as well as URLs for NNTP newsgroup(s).