From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: containers@lists.linux-foundation.org, linux-mm@kvack.org,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Pavel Emelyanov <xemul@openvz.org>,
Dan Malek <dan@embeddedalley.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH -mmotm 2/4] cgroups: remove events before destroying subsystem state objects
Date: Sat, 20 Feb 2010 13:22:17 +0900 [thread overview]
Message-ID: <20100220132217.17dc7dd3.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <a2717b1f5e0b49db7b6ecd1a5a41e65c1dc6b50a.1266618391.git.kirill@shutemov.name>
On Sat, 20 Feb 2010 00:28:17 +0200
"Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> Events should be removed after rmdir of cgroup directory, but before
> destroying subsystem state objects. Let's take reference to cgroup
> directory dentry to do that.
>
> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
Okay, I welcome this.
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hioryu@jp.fujitsu.com>
Just a quesion...After this change, if cgroup has remaining event,
cgroup is removed by workqueue of event->remove() -> d_put(), finally. Right ?
Do you have a test set for checking this behavior ?
Thanks,
-Kame
> ---
> include/linux/cgroup.h | 3 ---
> kernel/cgroup.c | 8 ++++++++
> mm/memcontrol.c | 9 ---------
> 3 files changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/include/linux/cgroup.h b/include/linux/cgroup.h
> index 64cebfe..1719c75 100644
> --- a/include/linux/cgroup.h
> +++ b/include/linux/cgroup.h
> @@ -395,9 +395,6 @@ struct cftype {
> * closes the eventfd or on cgroup removing.
> * This callback must be implemented, if you want provide
> * notification functionality.
> - *
> - * Be careful. It can be called after destroy(), so you have
> - * to keep all nesessary data, until all events are removed.
> */
> int (*unregister_event)(struct cgroup *cgrp, struct cftype *cft,
> struct eventfd_ctx *eventfd);
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index 46903cb..d142524 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -2979,6 +2979,7 @@ static void cgroup_event_remove(struct work_struct *work)
>
> eventfd_ctx_put(event->eventfd);
> kfree(event);
> + dput(cgrp->dentry);
> }
>
> /*
> @@ -3099,6 +3100,13 @@ static int cgroup_write_event_control(struct cgroup *cgrp, struct cftype *cft,
> goto fail;
> }
>
> + /*
> + * Events should be removed after rmdir of cgroup directory, but before
> + * destroying subsystem state objects. Let's take reference to cgroup
> + * directory dentry to do that.
> + */
> + dget(cgrp->dentry);
> +
> spin_lock(&cgrp->event_list_lock);
> list_add(&event->list, &cgrp->event_list);
> spin_unlock(&cgrp->event_list_lock);
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index a443c30..8fe6e7f 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -3358,12 +3358,6 @@ static int mem_cgroup_register_event(struct cgroup *cgrp, struct cftype *cft,
> }
> }
>
> - /*
> - * We need to increment refcnt to be sure that all thresholds
> - * will be unregistered before calling __mem_cgroup_free()
> - */
> - mem_cgroup_get(memcg);
> -
> if (type == _MEM)
> rcu_assign_pointer(memcg->thresholds, thresholds_new);
> else
> @@ -3457,9 +3451,6 @@ assign:
> /* To be sure that nobody uses thresholds before freeing it */
> synchronize_rcu();
>
> - for (i = 0; i < thresholds->size - size; i++)
> - mem_cgroup_put(memcg);
> -
> kfree(thresholds);
> unlock:
> mutex_unlock(&memcg->thresholds_lock);
> --
> 1.6.6.2
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-02-20 4:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 22:28 [PATCH -mmotm 1/4] cgroups: Fix race between userspace and kernelspace Kirill A. Shutemov
2010-02-19 22:28 ` [PATCH -mmotm 2/4] cgroups: remove events before destroying subsystem state objects Kirill A. Shutemov
2010-02-19 22:28 ` [PATCH -mmotm 3/4] cgroups: Add simple listener of cgroup events to documentation Kirill A. Shutemov
2010-02-19 22:28 ` [PATCH -mmotm 4/4] memcg: Update memcg_test.txt to describe memory thresholds Kirill A. Shutemov
2010-02-20 4:26 ` KAMEZAWA Hiroyuki
2010-02-20 4:24 ` [PATCH -mmotm 3/4] cgroups: Add simple listener of cgroup events to documentation KAMEZAWA Hiroyuki
2010-02-20 4:22 ` KAMEZAWA Hiroyuki [this message]
2010-02-20 11:56 ` [PATCH -mmotm 2/4] cgroups: remove events before destroying subsystem state objects Kirill A. Shutemov
2010-02-20 4:00 ` [PATCH -mmotm 1/4] cgroups: Fix race between userspace and kernelspace KAMEZAWA Hiroyuki
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=20100220132217.17dc7dd3.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dan@embeddedalley.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.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