Re: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
On 11/21/2013 01:35 AM, Tejun Heo wrote: > Hello, > > Sorry about the delay. > Oh, No problem, every members time resources are expensive, thank you for your reply. > On Fri, Nov 08, 2013 at 04:15:23PM +0800, Chen Gang wrote: >> After simplify, the related operation, environments and output are: >> >> [root@gchenlinux tmp]# df -Th | grep cgroup >> tmpfs tmpfs1001M 0 1001M 0% >> /sys/fs/cgroup >> [root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep >> systemd 1 root6r DIR 0,18 0 >> 5998 /sys/fs/cgroup/systemd/system >> [root@gchenlinux tmp]# cat /proc/cgroups >> #subsys_name hierarchy num_cgroups enabled >> cpuset 3 4 1 >> cpu4 35 1 >> cpuacct4 35 1 >> freezer5 4 1 >> [root@gchenlinux tmp]# mkdir cgroup >> [root@gchenlinux 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? > Hmm... I am not quit familiar about it, either, but at least I can contact related LTP members (I guess they can make sure about it). Excuse me, I am changing/finding new job, so I should not use Asianux Corporation mail again. And it seems I can not be focus on upstream kernel as much as before. :-( But at least, I will/should continue providing some contributions (more or less) to Public Open Source as volunteers. And for upstream kernel, I plan to make 1-3 patches per month (mainly for cross compiling). - if can not get companies support, I can not provide enough time resource on upstream kernel (I have to get pay check for family). - New company may mainly focus on open source tool chains (not only kernel), so I will/should also provide some contributions to them (e.g. KVM, GCC ...). At last, sorry again for I have to give up 10 patches per month for upstream kernel. Thanks. -- Chen Gang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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@gchenlinux tmp]# df -Th | grep cgroup > tmpfs tmpfs1001M 0 1001M 0% > /sys/fs/cgroup > [root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep > systemd 1 root6r DIR 0,18 0 > 5998 /sys/fs/cgroup/systemd/system > [root@gchenlinux tmp]# cat /proc/cgroups > #subsys_namehierarchy num_cgroups enabled > cpuset 3 4 1 > cpu 4 35 1 > cpuacct 4 35 1 > freezer 5 4 1 > [root@gchenlinux tmp]# mkdir cgroup > [root@gchenlinux 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
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@gchenlinux tmp]# df -Th | grep cgroup tmpfs tmpfs1001M 0 1001M 0% /sys/fs/cgroup [root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep systemd 1 root6r DIR 0,18 0 5998 /sys/fs/cgroup/systemd/system [root@gchenlinux tmp]# cat /proc/cgroups #subsys_namehierarchy num_cgroups enabled cpuset 3 4 1 cpu 4 35 1 cpuacct 4 35 1 freezer 5 4 1 [root@gchenlinux tmp]# mkdir cgroup [root@gchenlinux 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
On 11/21/2013 01:35 AM, Tejun Heo wrote: Hello, Sorry about the delay. Oh, No problem, every members time resources are expensive, thank you for your reply. On Fri, Nov 08, 2013 at 04:15:23PM +0800, Chen Gang wrote: After simplify, the related operation, environments and output are: [root@gchenlinux tmp]# df -Th | grep cgroup tmpfs tmpfs1001M 0 1001M 0% /sys/fs/cgroup [root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep systemd 1 root6r DIR 0,18 0 5998 /sys/fs/cgroup/systemd/system [root@gchenlinux tmp]# cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 3 4 1 cpu4 35 1 cpuacct4 35 1 freezer5 4 1 [root@gchenlinux tmp]# mkdir cgroup [root@gchenlinux 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? Hmm... I am not quit familiar about it, either, but at least I can contact related LTP members (I guess they can make sure about it). Excuse me, I am changing/finding new job, so I should not use Asianux Corporation mail again. And it seems I can not be focus on upstream kernel as much as before. :-( But at least, I will/should continue providing some contributions (more or less) to Public Open Source as volunteers. And for upstream kernel, I plan to make 1-3 patches per month (mainly for cross compiling). - if can not get companies support, I can not provide enough time resource on upstream kernel (I have to get pay check for family). - New company may mainly focus on open source tool chains (not only kernel), so I will/should also provide some contributions to them (e.g. KVM, GCC ...). At last, sorry again for I have to give up 10 patches per month for upstream kernel. Thanks. -- Chen Gang -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
