cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Jan Stancek <jstancek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Chen Gang
	<gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Garrett Cooper <yanegomi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	gaowanlong-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org,
	chris-8NJIiSa5LzA@public.gmane.org,
	mitani-Czb31pHLG9l3+QwDJ9on6Q@public.gmane.org,
	lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
Date: Fri, 22 Nov 2013 13:46:09 +0800	[thread overview]
Message-ID: <528EEFA1.7020408@huawei.com> (raw)
In-Reply-To: <1639659702.38807133.1385075581222.JavaMail.root-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

> ----- Original Message -----
>> From: "Tejun Heo" <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>> To: "Jan Stancek" <jstancek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> Cc: "Chen Gang" <gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, "Garrett Cooper" <yanegomi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, gaowanlong-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org,
>> chris-8NJIiSa5LzA@public.gmane.org, mitani-Czb31pHLG9l3+QwDJ9on6Q@public.gmane.org, lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org, "Li Zefan" <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
>> containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> Sent: Thursday, 21 November, 2013 4:26:45 PM
>> Subject: Re: [Suggestion] kernel: cgroup: mount failure in LTP cgroup_regression_test.sh
>>
>> Hello, Jan.
>>
>> On Thu, Nov 21, 2013 at 03:04:54AM -0500, Jan Stancek wrote:
>>> it looks like those 2 subsystems are already mounted by systemd,
>>> each in different hierarchy:
>>>
>>>>   cpuacct	4	35	1
>>>>   freezer	5	4	1
>>>
>>> from Documentation/cgroups/cgroups.txt:
>>> "If an active hierarchy with exactly the same set of subsystems already
>>> exists, it will be reused for the new mount. If no existing hierarchy
>>> matches, and any of the requested subsystems are in use in an existing
>>> hierarchy, the mount will fail with -EBUSY. Otherwise, a new hierarchy
>>> is activated, associated with the requested subsystems."
>>
>> Ah, cgroup now requires that those recycled mounts to have matching
>> options.  This is an intended behavior change because previously we
>> could end up with mounts which have actual options which differ from
>> what was specified by mount, which can be misleading at the very
>> least.
> 
> I believe the test always respected this requirement. Problem we see
> is because of initial state of the system. Test appears to expect
> that it is able to mount cgroups freely, but they are already in use.
> 
>> Would it be possible to update LTP accordingly?
> 
> I'm not sure the test can do anything (other than not run at all).
> 
> Other option is to setup system in a way where cgroups are not in use
> prior to running this test, though this may not be possible with systemd.
> 

I believe each test will do cleanup after it finishes (like umount
cgroupfs). I guess the system already mounted cgroupfs after boot
and each cgroup subsystem was mounted separately? And that leads to
this issue.

  parent reply	other threads:[~2013-11-22  5:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
     [not found]     ` <20131120173549.GO28946-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
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 [this message]
2013-11-22  5:49                           ` 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=528EEFA1.7020408@huawei.com \
    --to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=chris-8NJIiSa5LzA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=gaowanlong-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    --cc=jstancek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    --cc=mitani-Czb31pHLG9l3+QwDJ9on6Q@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=yanegomi-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).