mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menage <menage@google.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH] cgroups: fix lock inconsistency in cgroup_clone()
Date: Wed, 21 Jan 2009 02:05:49 -0800	[thread overview]
Message-ID: <6599ad830901210205jea6274rf898f59b9a48fa73@mail.gmail.com> (raw)
In-Reply-To: <497572AA.8020101@cn.fujitsu.com>

On Mon, Jan 19, 2009 at 10:43 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> I fixed a bug in cgroup_clone() in Linus' tree (commit 7b574b7), without
> noticing there was a cleanup patch in -mm tree that should be rebased
> (now commit 104cbd5), thus resulted in lock inconsistency.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>

Acked-by: Paul Menage <menage@google.com>

Thanks.

> ---
>
> for 2.6.29
>
> ---
>  kernel/cgroup.c |   13 +++++++------
>  1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index c298310..a5826f3 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -2991,20 +2991,21 @@ int cgroup_clone(struct task_struct *tsk, struct cgroup_subsys *subsys,
>                mutex_unlock(&cgroup_mutex);
>                return 0;
>        }
> -       task_lock(tsk);
> -       cg = tsk->cgroups;
> -       parent = task_cgroup(tsk, subsys->subsys_id);
>
>        /* Pin the hierarchy */
> -       if (!atomic_inc_not_zero(&parent->root->sb->s_active)) {
> +       if (!atomic_inc_not_zero(&root->sb->s_active)) {
>                /* We race with the final deactivate_super() */
>                mutex_unlock(&cgroup_mutex);
>                return 0;
>        }
>
>        /* Keep the cgroup alive */
> +       task_lock(tsk);
> +       parent = task_cgroup(tsk, subsys->subsys_id);
> +       cg = tsk->cgroups;
>        get_css_set(cg);
>        task_unlock(tsk);
> +
>        mutex_unlock(&cgroup_mutex);
>
>        /* Now do the VFS work to create a cgroup */
> @@ -3043,7 +3044,7 @@ int cgroup_clone(struct task_struct *tsk, struct cgroup_subsys *subsys,
>                mutex_unlock(&inode->i_mutex);
>                put_css_set(cg);
>
> -               deactivate_super(parent->root->sb);
> +               deactivate_super(root->sb);
>                /* The cgroup is still accessible in the VFS, but
>                 * we're not going to try to rmdir() it at this
>                 * point. */
> @@ -3069,7 +3070,7 @@ int cgroup_clone(struct task_struct *tsk, struct cgroup_subsys *subsys,
>        mutex_lock(&cgroup_mutex);
>        put_css_set(cg);
>        mutex_unlock(&cgroup_mutex);
> -       deactivate_super(parent->root->sb);
> +       deactivate_super(root->sb);
>        return ret;
>  }
>
> --
> 1.5.4.rc3
>
>
>

      reply	other threads:[~2009-01-21 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20  6:43 Li Zefan
2009-01-21 10:05 ` Paul Menage [this message]

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=6599ad830901210205jea6274rf898f59b9a48fa73@mail.gmail.com \
    --to=menage@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    /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®