summaryrefslogtreecommitdiff
path: root/usr
diff options
context:
space:
mode:
authorJeff Liu <jeff.liu@oracle.com>2013-05-26 21:33:09 +0800
committerTejun Heo <tj@kernel.org>2013-05-29 07:59:39 +0900
commit2a0ff3fbe39bc93f719ff857e5a359d9780579ff (patch)
tree49012c76db1739295a183043a065e1af6f8d4f19 /usr
parent7805d000db30a3787a4c969bab6ae4d8a5fd8ce6 (diff)
downloadlinux-3.10-2a0ff3fbe39bc93f719ff857e5a359d9780579ff.tar.gz
linux-3.10-2a0ff3fbe39bc93f719ff857e5a359d9780579ff.tar.bz2
linux-3.10-2a0ff3fbe39bc93f719ff857e5a359d9780579ff.zip
cgroup: warn about mismatching options of a new mount of an existing hierarchy
With the new __DEVEL__sane_behavior mount option was introduced, if the root cgroup is alive with no xattr function, to mount a new cgroup with xattr will be rejected in terms of design which just fine. However, if the root cgroup does not mounted with __DEVEL__sane_hehavior, to create a new cgroup with xattr option will succeed although after that the EA function does not works as expected but will get ENOTSUPP for setting up attributes under either cgroup. e.g. setfattr: /cgroup2/test: Operation not supported Instead of keeping silence in this case, it's better to drop a log entry in warning level. That would be helpful to understand the reason behind the scene from the user's perspective, and this is essentially an improvement does not break the backward compatibilities. With this fix, above mount attemption will keep up works as usual but the following line cound be found at the system log: [ ...] cgroup: new mount options do not match the existing superblock tj: minor formatting / message updates. Signed-off-by: Jie Liu <jeff.liu@oracle.com> Reported-by: Alexey Kodanev <alexey.kodanev@oracle.com> Signed-off-by: Tejun Heo <tj@kernel.org> Cc: stable@vger.kernel.org
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions