From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Martin Kepplinger <martink@posteo.de>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: perf: fix leaking rec_argv in error cases
Date: Fri, 15 Sep 2017 16:02:28 -0300 [thread overview]
Message-ID: <20170915190228.GE14469@kernel.org> (raw)
In-Reply-To: <20170913191419.29806-1-martink@posteo.de>
Em Wed, Sep 13, 2017 at 09:14:19PM +0200, Martin Kepplinger escreveu:
> Let's free the allocated rec_argv in case we return early, in
> order to avoid leaking memory.
>
> This adds free() at a few very similar places across the tree
> where it was missing.
Thanks, applied.
- Arnaldo
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> tools/perf/builtin-c2c.c | 1 +
> tools/perf/builtin-mem.c | 1 +
> tools/perf/builtin-timechart.c | 4 +++-
> tools/perf/builtin-trace.c | 1 +
> 4 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-c2c.c b/tools/perf/builtin-c2c.c
> index 475999e48f66..bb1ee22bd221 100644
> --- a/tools/perf/builtin-c2c.c
> +++ b/tools/perf/builtin-c2c.c
> @@ -2732,6 +2732,7 @@ static int perf_c2c__record(int argc, const char **argv)
> if (!perf_mem_events[j].supported) {
> pr_err("failed: event '%s' not supported\n",
> perf_mem_events[j].name);
> + free(rec_argv);
> return -1;
> }
>
> diff --git a/tools/perf/builtin-mem.c b/tools/perf/builtin-mem.c
> index 0f15634ef82c..6940490bc3f9 100644
> --- a/tools/perf/builtin-mem.c
> +++ b/tools/perf/builtin-mem.c
> @@ -112,6 +112,7 @@ static int __cmd_record(int argc, const char **argv, struct perf_mem *mem)
> if (!perf_mem_events[j].supported) {
> pr_err("failed: event '%s' not supported\n",
> perf_mem_events__name(j));
> + free(rec_argv);
> return -1;
> }
>
> diff --git a/tools/perf/builtin-timechart.c b/tools/perf/builtin-timechart.c
> index 4e2e61695986..01de01ca14f2 100644
> --- a/tools/perf/builtin-timechart.c
> +++ b/tools/perf/builtin-timechart.c
> @@ -1732,8 +1732,10 @@ static int timechart__io_record(int argc, const char **argv)
> if (rec_argv == NULL)
> return -ENOMEM;
>
> - if (asprintf(&filter, "common_pid != %d", getpid()) < 0)
> + if (asprintf(&filter, "common_pid != %d", getpid()) < 0) {
> + free(rec_argv);
> return -ENOMEM;
> + }
>
> p = rec_argv;
> for (i = 0; i < common_args_nr; i++)
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index 771ddab94bb0..dd8eec4c755c 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -2078,6 +2078,7 @@ static int trace__record(struct trace *trace, int argc, const char **argv)
> rec_argv[j++] = "syscalls:sys_enter,syscalls:sys_exit";
> else {
> pr_err("Neither raw_syscalls nor syscalls events exist.\n");
> + free(rec_argv);
> return -1;
> }
> }
> --
> 2.11.0
next prev parent reply other threads:[~2017-09-15 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 19:14 [PATCH] tools: perf: fix leaking rec_argv in error cases Martin Kepplinger
2017-09-15 19:02 ` Arnaldo Carvalho de Melo [this message]
2017-09-22 16:43 ` [tip:perf/core] perf tools: Fix " tip-bot for Martin Kepplinger
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=20170915190228.GE14469@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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