From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, will@kernel.org, ak@linux.intel.com,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
james.clark@arm.com, qiangqing.zhang@nxp.com
Subject: Re: [PATCH 1/6] perf jevents: Fix leak of mapfile memory
Date: Thu, 5 Mar 2020 12:13:52 -0300 [thread overview]
Message-ID: <20200305151352.GD7895@kernel.org> (raw)
In-Reply-To: <1583406486-154841-2-git-send-email-john.garry@huawei.com>
Em Thu, Mar 05, 2020 at 07:08:01PM +0800, John Garry escreveu:
> The memory for global pointer is never freed during normal program
> execution, so let's do that in the main function exit as a good programming
> practice.
>
> A stray blank line is also removed.
Thanks, applied to perf/urgent.
- Arnaldo
> Reported-by: Jiri Olsa <jolsa@redhat.com>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> tools/perf/pmu-events/jevents.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index 079c77b6a2fd..27b4da80f751 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -1082,10 +1082,9 @@ static int process_one_file(const char *fpath, const struct stat *sb,
> */
> int main(int argc, char *argv[])
> {
> - int rc;
> + int rc, ret = 0;
> int maxfds;
> char ldirname[PATH_MAX];
> -
> const char *arch;
> const char *output_file;
> const char *start_dirname;
> @@ -1156,7 +1155,8 @@ int main(int argc, char *argv[])
> /* Make build fail */
> fclose(eventsfp);
> free_arch_std_events();
> - return 1;
> + ret = 1;
> + goto out_free_mapfile;
> } else if (rc) {
> goto empty_map;
> }
> @@ -1174,14 +1174,17 @@ int main(int argc, char *argv[])
> /* Make build fail */
> fclose(eventsfp);
> free_arch_std_events();
> - return 1;
> + ret = 1;
> }
>
> - return 0;
> +
> + goto out_free_mapfile;
>
> empty_map:
> fclose(eventsfp);
> create_empty_mapping(output_file);
> free_arch_std_events();
> - return 0;
> +out_free_mapfile:
> + free(mapfile);
> + return ret;
> }
> --
> 2.17.1
>
--
- Arnaldo
next prev parent reply other threads:[~2020-03-05 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 11:08 [PATCH 0/6] perf test pmu-events case John Garry
2020-03-05 11:08 ` [PATCH 1/6] perf jevents: Fix leak of mapfile memory John Garry
2020-03-05 15:13 ` Arnaldo Carvalho de Melo [this message]
2020-03-07 7:36 ` [tip: perf/urgent] " tip-bot2 for John Garry
2020-03-05 11:08 ` [PATCH 2/6] perf jevents: Support test events folder John Garry
2020-03-05 11:08 ` [PATCH 3/6] perf jevents: Add some test events John Garry
2020-03-05 11:08 ` [PATCH 4/6] perf pmu: Refactor pmu_add_cpu_aliases() John Garry
2020-03-05 11:08 ` [PATCH 5/6] perf pmu: Add is_pmu_core() John Garry
2020-03-05 11:08 ` [PATCH 6/6] perf test: Add pmu-events test John Garry
2020-03-09 8:49 ` Jiri Olsa
2020-03-09 10:12 ` John Garry
2020-03-09 15:26 ` Jiri Olsa
2020-03-09 16:20 ` John Garry
2020-03-13 10:32 ` Jiri Olsa
2020-03-13 11:08 ` John Garry
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=20200305151352.GD7895@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=qiangqing.zhang@nxp.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.