[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131120173549.GO28946@htj.dyndns.org>
Date: Wed, 20 Nov 2013 12:35:49 -0500
From: Tejun Heo <tj@...nel.org>
To: Chen Gang <gang.chen@...anux.com>
Cc: Li Zefan <lizefan@...wei.com>,
containers@...ts.linux-foundation.org, cgroups@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Suggestion] kernel: cgroup: mount failure in LTP
cgroup_regression_test.sh
Hello,
Sorry about the delay.
On Fri, Nov 08, 2013 at 04:15:23PM +0800, Chen Gang wrote:
> After simplify, the related operation, environments and output are:
>
> [root@...enlinux tmp]# df -Th | grep cgroup
> tmpfs tmpfs 1001M 0 1001M 0% /sys/fs/cgroup
> [root@...enlinux tmp]# lsof | grep cgroup | grep -v grep
> systemd 1 root 6r DIR 0,18 0 5998 /sys/fs/cgroup/systemd/system
> [root@...enlinux tmp]# cat /proc/cgroups
> #subsys_name hierarchy num_cgroups enabled
> cpuset 3 4 1
> cpu 4 35 1
> cpuacct 4 35 1
> freezer 5 4 1
> [root@...enlinux tmp]# mkdir cgroup
> [root@...enlinux tmp]# mount -t cgroup -o freezer,cpuacct xxx cgroup/
> mount: xxx already mounted or cgroup/ busy
>
> Is it real issue of cgroup? If it is, I will/should continue analyzing.
Hmmm... I'm a bit confused. What is it testing? "cat /proc/cgroup"
is showing that freezer is already mounted and the kernel seems to
have correctly refused to mount it in a different hierarchy. What am
I missing here?
Thanks.
--
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