From: Vivek Goyal <vgoyal@redhat.com>
To: jaxboe@fusionio.com, Jens Axboe <axboe@kernel.dk>
Cc: tj@kernel.org, linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] blk-throttle: Free up policy node associated with deleted rule
Date: Tue, 25 Oct 2011 09:36:25 -0400 [thread overview]
Message-ID: <20111025133625.GA23292@redhat.com> (raw)
In-Reply-To: <1319144906-5066-1-git-send-email-vgoyal@redhat.com>
On Thu, Oct 20, 2011 at 05:08:25PM -0400, Vivek Goyal wrote:
> If a rule is being deleted, free up associated policy node. Otherwise
> that memory is leaked.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Hi Jens,
Do you see any issues with the two patches. Can you please consider these
for merging.
Thanks
Vivek
> ---
> block/blk-cgroup.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index b596e54..4ddf11f 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -1085,6 +1085,7 @@ static int blkiocg_file_write(struct cgroup *cgrp, struct cftype *cft,
>
> if (blkio_delete_rule_command(newpn)) {
> blkio_policy_delete_node(pn);
> + kfree(pn);
> spin_unlock_irq(&blkcg->lock);
> goto update_io_group;
> }
> --
> 1.7.4.4
next prev parent reply other threads:[~2011-10-25 13:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 21:08 Vivek Goyal
2011-10-20 21:08 ` [PATCH 2/2] blk-throttle: Take blkcg->lock while traversing blkcg->policy_list Vivek Goyal
2011-10-20 21:11 ` Tejun Heo
2011-10-20 21:20 ` Vivek Goyal
2011-10-20 21:29 ` Tejun Heo
2011-10-21 12:10 ` Vivek Goyal
2011-10-25 14:13 ` Jens Axboe
2011-10-25 19:01 ` Vivek Goyal
2011-10-20 21:09 ` [PATCH 1/2] blk-throttle: Free up policy node associated with deleted rule Tejun Heo
2011-10-25 13:36 ` Vivek Goyal [this message]
2011-10-25 13:45 ` Jens Axboe
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=20111025133625.GA23292@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome