From: kajoljain <kjain@linux.ibm.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Rob Herring <robh@kernel.org>
Cc: Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v2 1/4] libperf evsel: Open shouldn't leak fd on failure
Date: Thu, 9 Jun 2022 11:09:15 +0530 [thread overview]
Message-ID: <4ae75240-0673-5429-2d03-54050e7013c2@linux.ibm.com> (raw)
In-Reply-To: <20220609052355.1300162-2-irogers@google.com>
On 6/9/22 10:53, Ian Rogers wrote:
> If the perf_event_open fails the fd is opened but the fd is only freed
> by closing (not by delete). Typically when an open fails you don't call
> close and so this results in a memory leak. To avoid this, add a close
> when open fails.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/lib/perf/evsel.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
Patch looks fine to me
Reviewed-By: Kajol Jain<kjain@linux.ibm.com>
>
> diff --git a/tools/lib/perf/evsel.c b/tools/lib/perf/evsel.c
> index c1d58673f6ef..952f3520d5c2 100644
> --- a/tools/lib/perf/evsel.c
> +++ b/tools/lib/perf/evsel.c
> @@ -149,23 +149,30 @@ int perf_evsel__open(struct perf_evsel *evsel, struct perf_cpu_map *cpus,
> int fd, group_fd, *evsel_fd;
>
> evsel_fd = FD(evsel, idx, thread);
> - if (evsel_fd == NULL)
> - return -EINVAL;
> + if (evsel_fd == NULL) {
> + err = -EINVAL;
> + goto out;
> + }
>
> err = get_group_fd(evsel, idx, thread, &group_fd);
> if (err < 0)
> - return err;
> + goto out;
>
> fd = sys_perf_event_open(&evsel->attr,
> threads->map[thread].pid,
> cpu, group_fd, 0);
>
> - if (fd < 0)
> - return -errno;
> + if (fd < 0) {
> + err = -errno;
> + goto out;
> + }
>
> *evsel_fd = fd;
> }
> }
> +out:
> + if (err)
> + perf_evsel__close(evsel);
>
> return err;
> }
next prev parent reply other threads:[~2022-06-09 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 5:23 [PATCH v2 0/4] Tidy user rdpmc documentation and testing Ian Rogers
2022-06-09 5:23 ` [PATCH v2 1/4] libperf evsel: Open shouldn't leak fd on failure Ian Rogers
2022-06-09 5:39 ` kajoljain [this message]
2022-06-09 5:23 ` [PATCH v2 2/4] perf: Align user space counter reading with code Ian Rogers
2022-07-19 17:45 ` Rob Herring
2022-07-19 22:42 ` Ian Rogers
2022-06-09 5:23 ` [PATCH v2 3/4] perf test: Remove x86 rdpmc test Ian Rogers
2022-06-09 5:23 ` [PATCH v2 4/4] perf test: Add user space counter reading tests Ian Rogers
2022-06-09 5:40 ` kajoljain
2022-07-19 15:50 ` [PATCH v2 0/4] Tidy user rdpmc documentation and testing Ian Rogers
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=4ae75240-0673-5429-2d03-54050e7013c2@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@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