From: Ingo Molnar <mingo@elte.hu>
To: Paul Menage <menage@google.com>
Cc: akpm@linux-foundation.org, serue@us.ibm.com,
linux-kernel@vger.kernel.org, containers@lists.osdl.org
Subject: Re: [PATCH] cgroup: Fix root_count when mount fails due to busy subsystem
Date: Fri, 23 Jan 2009 19:10:56 +0100 [thread overview]
Message-ID: <20090123181056.GA31142@elte.hu> (raw)
In-Reply-To: <20090123004703.25103.29754.stgit@menage.corp.google.com>
* Paul Menage <menage@google.com> wrote:
> cgroup: Fix root_count when mount fails due to busy subsystem
>
> root_count was being incremented in cgroup_get_sb() after all error
> checking was complete, but decremented in cgroup_kill_sb(), which can be
> called on a superblock that we gave up on due to an error. This patch
> changes cgroup_kill_sb() to only decrement root_count if the root was
> previously linked into the list of roots.
i'm wondering, what happens in the buggy case: does cgroup_kill_sb() get
called twice (if yes, why?), or do we call cgroup_kill_sb() on a not yet
added sb and hence root_count has not been elevated yet? (if yes, which
codepath does this?)
The error handling in cgroup_get_sb() definitely seems a bit twisted -
find below a few error path and other cleanups.
Thanks,
Ingo
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index c298310..28d1b67 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -1025,18 +1026,12 @@ static int cgroup_get_sb(struct file_system_type *fs_type,
* have some link structures left over
*/
ret = allocate_cg_links(css_set_count, &tmp_cg_links);
- if (ret) {
- mutex_unlock(&cgroup_mutex);
- mutex_unlock(&inode->i_mutex);
- goto drop_new_super;
- }
+ if (ret)
+ goto drop_new_super_unlock;
ret = rebind_subsystems(root, root->subsys_bits);
- if (ret == -EBUSY) {
- mutex_unlock(&cgroup_mutex);
- mutex_unlock(&inode->i_mutex);
+ if (ret == -EBUSY)
goto free_cg_links;
- }
/* EBUSY should be the only error here */
BUG_ON(ret);
@@ -1075,18 +1070,24 @@ static int cgroup_get_sb(struct file_system_type *fs_type,
free_cg_links:
free_cg_links(&tmp_cg_links);
+
+ drop_new_super_unlock:
+ mutex_unlock(&cgroup_mutex);
+ mutex_unlock(&inode->i_mutex);
drop_new_super:
up_write(&sb->s_umount);
deactivate_super(sb);
+
return ret;
}
-static void cgroup_kill_sb(struct super_block *sb) {
+static void cgroup_kill_sb(struct super_block *sb)
+{
struct cgroupfs_root *root = sb->s_fs_info;
struct cgroup *cgrp = &root->top_cgroup;
- int ret;
- struct cg_cgroup_link *link;
struct cg_cgroup_link *saved_link;
+ struct cg_cgroup_link *link;
+ int ret;
BUG_ON(!root);
next prev parent reply other threads:[~2009-01-23 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:48 [PATCH] cgroup: Fix root_count when mount fails due to busy subsystem Paul Menage
2009-01-23 2:20 ` Serge E. Hallyn
2009-01-23 10:22 ` Ingo Molnar
2009-01-23 16:59 ` Paul Menage
2009-01-23 17:50 ` Ingo Molnar
2009-01-23 18:10 ` Ingo Molnar [this message]
2009-01-23 18:32 ` Paul Menage
2009-01-23 18:36 ` Ingo Molnar
2009-01-23 18:42 ` Paul Menage
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=20090123181056.GA31142@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=serue@us.ibm.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