From: Paul Menage <menage@google.com>
To: akpm@linux-foundation.org, serue@us.ibm.com
Cc: linux-kernel@vger.kernel.org, containers@lists.osdl.org
Subject: [PATCH] cgroup: Fix root_count when mount fails due to busy subsystem
Date: Thu, 22 Jan 2009 16:48:41 -0800 [thread overview]
Message-ID: <20090123004703.25103.29754.stgit@menage.corp.google.com> (raw)
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.
Signed-off-by: Paul Menage <menage@google.com>
---
I was actually surprised to find that list_del() doesn't crash when
run on an unattached list_head structure.
kernel/cgroup.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index adcd0bb..9ce27e8 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -1115,8 +1115,10 @@ static void cgroup_kill_sb(struct super_block *sb) {
}
write_unlock(&css_set_lock);
- list_del(&root->root_list);
- root_count--;
+ if (!list_empty(&root->root_list)) {
+ list_del(&root->root_list);
+ root_count--;
+ }
mutex_unlock(&cgroup_mutex);
next reply other threads:[~2009-01-23 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:48 Paul Menage [this message]
2009-01-23 2:20 ` [PATCH] cgroup: Fix root_count when mount fails due to busy subsystem 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
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=20090123004703.25103.29754.stgit@menage.corp.google.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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