From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Akinobu Mita" <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Christoph Lameter" <clameter@sgi.com>,
"Gautham R Shenoy" <ego@in.ibm.com>
Subject: Re: [patch 2/9] slab: fix memory leak in cpu hotplug error path
Date: Tue, 24 Jul 2007 12:46:12 +0300 [thread overview]
Message-ID: <84144f020707240246v4ebe2c57r8cccf6f09e02a1e9@mail.gmail.com> (raw)
In-Reply-To: <20070722153342.726607571@gmail.com>
On 7/22/07, Akinobu Mita <akinobu.mita@gmail.com> wrote:
> This patch fixes memory leak in error path.
>
> In reality, we don't need to call cpuup_canceled(cpu) for now.
> But upcoming cpu hotplug error handling change needs this.
This and the previous patch look good to me.
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
next prev parent reply other threads:[~2007-07-24 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 15:33 [patch 0/9] CPU hotplug error handling fixes take2 Akinobu Mita
2007-07-22 15:33 ` [patch 1/9] slab: cleanup cpuup_callback() Akinobu Mita
2007-07-22 15:33 ` [patch 2/9] slab: fix memory leak in cpu hotplug error path Akinobu Mita
2007-07-24 9:46 ` Pekka Enberg [this message]
2007-07-22 15:33 ` [patch 3/9] cpu: deliver CPU_UP_CANCELED only to NOTIFY_OKed callbacks with CPU_UP_PREPARE Akinobu Mita
2007-07-22 23:48 ` Rusty Russell
2007-07-22 15:33 ` [patch 4/9] topology: remove topology_dev_map Akinobu Mita
2007-07-23 23:16 ` Greg KH
2007-07-22 15:33 ` [patch 5/9] thermal_throttle: fix cpu hotplug error handling Akinobu Mita
2007-07-22 15:33 ` [patch 6/9] msr: " Akinobu Mita
2007-07-22 15:33 ` [patch 7/9] cpuid: " Akinobu Mita
2007-07-22 15:33 ` [patch 8/9] mce: " Akinobu Mita
2007-07-22 15:33 ` [patch 9/9] intel_cacheinfo: " Akinobu Mita
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=84144f020707240246v4ebe2c57r8cccf6f09e02a1e9@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akinobu.mita@gmail.com \
--cc=clameter@sgi.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®