From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Ingo Molnar <mingo@elte.hu>, Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] hw breakpoint: Fix possible memory leak
Date: Mon, 27 Feb 2012 11:33:05 +0100 [thread overview]
Message-ID: <1330338785.11248.49.camel@twins> (raw)
In-Reply-To: <1330311739-24302-1-git-send-email-namhyung.kim@lge.com>
On Mon, 2012-02-27 at 12:02 +0900, Namhyung Kim wrote:
> If kzalloc() for TYPE_DATA failed on a given cpu, previous chunk
> will be leaked. Fix it.
so why not fix the error loop? wouldn't putting that err_cpu == cpu
break after the kfree sort it?
> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
> ---
> kernel/events/hw_breakpoint.c | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/events/hw_breakpoint.c b/kernel/events/hw_breakpoint.c
> index b0309f76d777..58298b0d0e92 100644
> --- a/kernel/events/hw_breakpoint.c
> +++ b/kernel/events/hw_breakpoint.c
> @@ -645,8 +645,12 @@ int __init init_hw_breakpoint(void)
> task_bp_pinned = &per_cpu(nr_task_bp_pinned[i], cpu);
> *task_bp_pinned = kzalloc(sizeof(int) * nr_slots[i],
> GFP_KERNEL);
> - if (!*task_bp_pinned)
> + if (!*task_bp_pinned) {
> + while (--i >= 0)
> + kfree(per_cpu(nr_task_bp_pinned[i],
> + cpu));
> goto err_alloc;
> + }
> }
> }
>
next prev parent reply other threads:[~2012-02-27 10:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 3:02 [PATCH] hw breakpoint: Fix possible memory leak Namhyung Kim
2012-02-27 10:33 ` Peter Zijlstra [this message]
2012-02-27 10:44 ` Ingo Molnar
2012-02-27 11:04 ` Peter Zijlstra
2012-02-27 11:56 ` Ingo Molnar
2012-02-27 13:32 ` Namhyung Kim
2012-02-27 19:40 ` Ingo Molnar
2012-02-27 23:38 ` Frederic Weisbecker
2012-02-28 1:19 ` [PATCH v2] hw breakpoint: Fix a " Namhyung Kim
2012-02-28 9:13 ` [tip:perf/urgent] perf/hwbp: " tip-bot for Namhyung Kim
2012-02-27 12:45 ` [PATCH] hw breakpoint: Fix " Namhyung Kim
2012-02-27 12:46 ` Peter Zijlstra
2012-02-27 12:50 ` Namhyung Kim
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=1330338785.11248.49.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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.