From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, lizefan@huawei.com,
cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup fixes for v3.17-rc6
Date: Tue, 23 Sep 2014 02:33:53 -0400 [thread overview]
Message-ID: <20140923063353.GK11740@mtj.dyndns.org> (raw)
Hello, Linus.
One late fix for cgroup. I was waiting for another set of fixes for a
long-standing obscure cpuset bug but am not sure whether they'll be
ready before v3.17 release. This one is a simple fix for a mutex
unlock balance bug, which is detected by coccinelle and probably won't
trigger in the wild, introduced during this devel cycle.
Thanks.
The following changes since commit aa32362f011c6e863132b16c1761487166a4bad2:
cgroup: check cgroup liveliness before unbreaking kernfs (2014-09-05 01:36:19 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-3.17-fixes
for you to fetch changes up to eb4aec84d6bdf98d00cedb41c18000f7a31e648a:
cgroup: fix unbalanced locking (2014-09-18 12:32:52 -0400)
----------------------------------------------------------------
Zefan Li (1):
cgroup: fix unbalanced locking
kernel/cgroup.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 940aced..3a73f99 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -3985,7 +3985,6 @@ static int pidlist_array_load(struct cgroup *cgrp, enum cgroup_filetype type,
l = cgroup_pidlist_find_create(cgrp, type);
if (!l) {
- mutex_unlock(&cgrp->pidlist_mutex);
pidlist_free(array);
return -ENOMEM;
}
--
tejun
next reply other threads:[~2014-09-23 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 6:33 Tejun Heo [this message]
2014-09-23 6:45 ` Zefan Li
2014-09-23 13:05 ` Tejun Heo
2014-09-23 13:10 ` [GIT UPDATED " Tejun Heo
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=20140923063353.GK11740@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®