linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for Namhyung Kim <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, a.p.zijlstra@chello.nl, acme@redhat.com,
	linux-kernel@vger.kernel.org, mingo@kernel.org,
	masami.hiramatsu.pt@hitachi.com, hpa@zytor.com,
	wangnan0@huawei.com, jolsa@redhat.com, namhyung@kernel.org
Subject: [tip:perf/core] perf probe: Free perf_probe_event in cleanup_perf_probe_events()
Date: Wed, 16 Sep 2015 00:28:01 -0700	[thread overview]
Message-ID: <tip-a43aac299c3abc09eff856039f5b72166b780d35@git.kernel.org> (raw)
In-Reply-To: <1441852026-28974-1-git-send-email-namhyung@kernel.org>

Commit-ID:  a43aac299c3abc09eff856039f5b72166b780d35
Gitweb:     http://git.kernel.org/tip/a43aac299c3abc09eff856039f5b72166b780d35
Author:     Namhyung Kim <namhyung@kernel.org>
AuthorDate: Thu, 10 Sep 2015 11:27:04 +0900
Committer:  Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Tue, 15 Sep 2015 09:48:32 -0300

perf probe: Free perf_probe_event in cleanup_perf_probe_events()

The cleanup_perf_probe_events() frees all resources related to a perf
probe event.  However it only freed resources in trace probe events, not
perf probe events.  So call clear_perf_probe_event() too.

Reported-by: Wang Nan <wangnan0@huawei.com>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1441852026-28974-1-git-send-email-namhyung@kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
 tools/perf/util/probe-event.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
index 5964ecc..3d7d60c 100644
--- a/tools/perf/util/probe-event.c
+++ b/tools/perf/util/probe-event.c
@@ -2792,6 +2792,7 @@ void cleanup_perf_probe_events(struct perf_probe_event *pevs, int npevs)
 			clear_probe_trace_event(&pevs[i].tevs[j]);
 		zfree(&pevs[i].tevs);
 		pevs[i].ntevs = 0;
+		clear_perf_probe_event(&pevs[i]);
 	}
 
 	exit_symbol_maps();

      parent reply	other threads:[~2015-09-16  7:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  2:27 [PATCH 1/3] perf probe: Free perf probe event in cleanup_perf_probe_events() Namhyung Kim
2015-09-10  2:27 ` [PATCH 2/3] perf probe: Export init/exit_probe_symbol_maps() Namhyung Kim
2015-09-10 12:56   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-16  7:28   ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-09-10  2:27 ` [PATCH 3/3] perf probe: Move init/exit_probe_symbol_maps() into callers Namhyung Kim
2015-09-10 12:58   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-11 15:52     ` Namhyung Kim
2015-09-14 18:18       ` Arnaldo Carvalho de Melo
2015-09-10  8:51 ` [PATCH 1/3] perf probe: Free perf probe event in cleanup_perf_probe_events() 平松雅巳 / HIRAMATU,MASAMI
2015-09-16  7:28 ` tip-bot for Namhyung Kim [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=tip-a43aac299c3abc09eff856039f5b72166b780d35@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangnan0@huawei.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).