From: Namhyung Kim <namhyung@gmail.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: acme@kernel.org, jolsa@kernel.org, mitake@dcl.info.waseda.ac.jp,
aswin@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/9] perf bench: sched-messaging: Plug memleak
Date: Thu, 19 Jun 2014 15:20:06 +0900 [thread overview]
Message-ID: <8738f18lpl.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1402942467-10671-5-git-send-email-davidlohr@hp.com> (Davidlohr Bueso's message of "Mon, 16 Jun 2014 11:14:22 -0700")
On Mon, 16 Jun 2014 11:14:22 -0700, Davidlohr Bueso wrote:
> Explicitly free the thread array ('pth_tab').
It seems like sender/receiver contexts were also leaked.
Thanks,
Namhyung
next prev parent reply other threads:[~2014-06-19 6:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 18:14 [PATCH 0/9] perf bench: Updates for 3.17 Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 1/9] perf bench: Add --repeat option Davidlohr Bueso
2014-06-19 6:14 ` Namhyung Kim
2014-06-19 11:45 ` Davidlohr Bueso
2014-06-19 23:51 ` Namhyung Kim
2014-06-20 3:03 ` Davidlohr Bueso
2014-06-24 5:54 ` Namhyung Kim
2014-06-25 5:51 ` [tip:perf/core] " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 2/9] perf bench: sched-messaging: Redo runtime output Davidlohr Bueso
2014-06-19 19:30 ` Arnaldo Carvalho de Melo
2014-06-16 18:14 ` [PATCH 3/9] perf bench: sched-messaging: Support multiple runs Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 4/9] perf bench: sched-messaging: Plug memleak Davidlohr Bueso
2014-06-19 6:20 ` Namhyung Kim [this message]
2014-06-25 5:51 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 5/9] perf bench: futex: Use global --repeat option Davidlohr Bueso
2014-06-25 5:51 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 6/9] perf bench: futex: Replace --silent option with global --format Davidlohr Bueso
2014-06-19 16:38 ` Arnaldo Carvalho de Melo
2014-06-19 17:01 ` Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 7/9] perf bench: mem: -o and -n options are mutually exclusive Davidlohr Bueso
2014-06-25 5:52 ` [tip:perf/core] perf bench mem: The " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 8/9] perf bench: sched-messaging: Drop barf() Davidlohr Bueso
2014-06-25 5:52 ` [tip:perf/core] perf bench " tip-bot for Davidlohr Bueso
2014-06-16 18:14 ` [PATCH 9/9] perf bench: futex: Support operations for shared futexes Davidlohr Bueso
2014-06-19 16:41 ` Arnaldo Carvalho de Melo
2014-06-19 16:43 ` Davidlohr Bueso
2014-06-19 17:05 ` Arnaldo Carvalho de Melo
2014-06-19 19:48 ` Darren Hart
2014-06-25 17:07 ` Davidlohr Bueso
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=8738f18lpl.fsf@sejong.aot.lge.com \
--to=namhyung@gmail.com \
--cc=acme@kernel.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
/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.