[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140908012025.GF5061@mtj.dyndns.org>
Date: Mon, 8 Sep 2014 10:20:25 +0900
From: Tejun Heo <tj@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
cgroups@...r.kernel.org
Subject: [GIT PULL] cgroup fixes for v3.17-rc4
Hello, Linus.
Up until now, cgroup has allowed any character including '\n' in
cgroup names; unfortunately, as '\n' is used as the row delimiter in
/proc/$PID/cgroup, '\n' in a cgroup name makes the content of the file
ambiguous to parse. This pull request includes Alban's patch to
disallow '\n' in cgroup names. While this is a userland visible
behavior change, given the craziness of allowing '\n' and its
implications, I believe the change is justified. The patch is marked
for -stable backport.
Two other patches from Li to fix a possible oops when cgroup
destruction races against other file operations and one from Vivek to
fix a unified hierarchy devel behavior.
Thanks.
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
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 aa32362f011c6e863132b16c1761487166a4bad2:
cgroup: check cgroup liveliness before unbreaking kernfs (2014-09-05 01:36:19 +0900)
----------------------------------------------------------------
Alban Crequy (1):
cgroup: reject cgroup names with '\n'
Li Zefan (2):
cgroup: delay the clearing of cgrp->kn->priv
cgroup: check cgroup liveliness before unbreaking kernfs
Vivek Goyal (1):
cgroup: Display legacy cgroup files on default hierarchy
kernel/cgroup.c | 47 +++++++++++++++++++++++++++++++++--------------
1 file changed, 33 insertions(+), 14 deletions(-)
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists