From: Chen Gang <gang.chen-bOixZGp5f+dBDgjK7y7TUQ@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
Date: Fri, 08 Nov 2013 16:15:23 +0800 [thread overview]
Message-ID: <527C9D9B.8090802@asianux.com> (raw)
Hello Maintainers:
On Fedora16 with defconfig for next-20131107 kernel, use latest LTP
(Linux Test Project) version, test_5() in cgroup_regression_test.sh
will be fail. The related LTP output:
<<<test_start>>>
tag=cgroup stime=1383562810
cmdline=" cgroup_regression_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
cgroup_regression_test 1 TPASS : no kernel bug was found
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 118: 13283 Terminated ./fork_processes
cgroup_regression_test 2 TPASS : notify_on_release is inherited
cgroup_regression_test 3 TCONF : CONFIG_SCHED_DEBUG is not enabled
cgroup_regression_test 4 TCONF : CONFIG_LOCKDEP is not enabled
mount: xxx already mounted or cgroup/ busy
cgroup_regression_test 5 TFAIL : mount freezer and cpuacct failed
cgroup_regression_test 6 TCONF : CONFIG_CGROUP_NS
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 360: 24428 Terminated sleep 100 < cgroup/0
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 381: 24447 Terminated sleep 100 < cgroup/0
cgroup_regression_test 7 TPASS : no kernel bug was found
cgroup_regression_test 8 TPASS : no kernel bug was found
cgroup_regression_test 9 TPASS : no kernel warning was found
rmdir: failed to remove `cgroup/0': No such file or directory
umount: /sys/fs/cgroup/systemd: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
cgroup_regression_test 10 TPASS : no kernel warning was found
<<<execution_status>>>
initiation_status="ok"
duration=62 termination_type=exited termination_id=1 corefile=no
cutime=3341 cstime=6353
<<<test_end>>>
After simplify, the related operation, environments and output are:
[root@gchenlinux tmp]# df -Th | grep cgroup
tmpfs tmpfs 1001M 0 1001M 0% /sys/fs/cgroup
[root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep
systemd 1 root 6r 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
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.
Welcome any additional suggestions and completions.
Thanks.
--
Chen Gang
WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>
Cc: containers@lists.linux-foundation.org, cgroups@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
Date: Fri, 08 Nov 2013 16:15:23 +0800 [thread overview]
Message-ID: <527C9D9B.8090802@asianux.com> (raw)
Hello Maintainers:
On Fedora16 with defconfig for next-20131107 kernel, use latest LTP
(Linux Test Project) version, test_5() in cgroup_regression_test.sh
will be fail. The related LTP output:
<<<test_start>>>
tag=cgroup stime=1383562810
cmdline=" cgroup_regression_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
cgroup_regression_test 1 TPASS : no kernel bug was found
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 118: 13283 Terminated ./fork_processes
cgroup_regression_test 2 TPASS : notify_on_release is inherited
cgroup_regression_test 3 TCONF : CONFIG_SCHED_DEBUG is not enabled
cgroup_regression_test 4 TCONF : CONFIG_LOCKDEP is not enabled
mount: xxx already mounted or cgroup/ busy
cgroup_regression_test 5 TFAIL : mount freezer and cpuacct failed
cgroup_regression_test 6 TCONF : CONFIG_CGROUP_NS
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 360: 24428 Terminated sleep 100 < cgroup/0
/opt/ltp/testcases/bin/cgroup_regression_test.sh: line 381: 24447 Terminated sleep 100 < cgroup/0
cgroup_regression_test 7 TPASS : no kernel bug was found
cgroup_regression_test 8 TPASS : no kernel bug was found
cgroup_regression_test 9 TPASS : no kernel warning was found
rmdir: failed to remove `cgroup/0': No such file or directory
umount: /sys/fs/cgroup/systemd: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
cgroup_regression_test 10 TPASS : no kernel warning was found
<<<execution_status>>>
initiation_status="ok"
duration=62 termination_type=exited termination_id=1 corefile=no
cutime=3341 cstime=6353
<<<test_end>>>
After simplify, the related operation, environments and output are:
[root@gchenlinux tmp]# df -Th | grep cgroup
tmpfs tmpfs 1001M 0 1001M 0% /sys/fs/cgroup
[root@gchenlinux tmp]# lsof | grep cgroup | grep -v grep
systemd 1 root 6r 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
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.
Welcome any additional suggestions and completions.
Thanks.
--
Chen Gang
next reply other threads:[~2013-11-08 8:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 8:15 Chen Gang [this message]
2013-11-08 8:15 ` [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh Chen Gang
[not found] ` <527C9D9B.8090802-bOixZGp5f+dBDgjK7y7TUQ@public.gmane.org>
2013-11-20 17:35 ` Tejun Heo
2013-11-20 17:35 ` Tejun Heo
[not found] ` <20131120173549.GO28946-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-11-21 2:21 ` Chen Gang
2013-11-21 2:21 ` Chen Gang
[not found] ` <528D6E19.4080100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-21 4:18 ` Fwd: " Chen Gang
[not found] ` <528D89AA.6080102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-21 8:04 ` Jan Stancek
[not found] ` <551116969.38084288.1385021094494.JavaMail.root-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-21 9:19 ` Chen Gang
2013-11-21 15:26 ` Tejun Heo
[not found] ` <20131121152645.GB3352-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-11-21 23:13 ` Jan Stancek
[not found] ` <1639659702.38807133.1385075581222.JavaMail.root-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-22 5:46 ` Li Zefan
2013-11-22 5:46 ` Li Zefan
2013-11-22 5:49 ` Tejun Heo
2013-11-22 5:49 ` Tejun Heo
2013-11-21 15:26 ` Tejun Heo
2013-11-21 4:18 ` Fwd: " Chen Gang
2013-11-20 17:35 ` 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=527C9D9B.8090802@asianux.com \
--to=gang.chen-boixzgp5f+dbdgjk7y7tuq@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.