From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Waiman Long <longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cgroup: Show control files in cgroup2 root after mount
Date: Tue, 18 Jul 2017 16:12:29 -0400 [thread overview]
Message-ID: <20170718201229.GD3365493@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <539870d2-8b85-2f54-61bd-4ba068e75ce0-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hello,
On Tue, Jul 18, 2017 at 04:00:45PM -0400, Waiman Long wrote:
> From my own debugging, the controller files (e.g. the debug controller)
> were indirectly populated by the rebind_subsystems() call.
>
> [ 1.628103] css_populate_dir: init subsystem debug
...
> [ 1.654975] cgroup_apply_control_enable+0x103/0x340
> [ 1.657719] cgroup_apply_control+0x1a/0x30
> [ 1.658521] rebind_subsystems+0x18a/0x3b0
...
But there's kernfs_activate() call at the end of rebind_subsystems(),
so if the files were being added there, it should have been activated
there and I can confirm that the files are correctly added / removed
from the cgroup2 root directory when controllers are attached to /
detached from it.
> For the default cgroup2 root, kernfs_activate() was only called at the
> beginning in cgroup_init() with only the base cgroup files added. No
> more call after that until I touched the cgroup.subtree_control file.
Hmm... we're activating at the end of
* cgroup_setup_root()
* rebind_subsystems()
* cgroup_subtree_control_write()
* cgroup_apply_cftypes() after successful addition
* cgroup_mkdir()
I *think* this should cover everything. Just in case, are you looking
at the mainline kernel? Can you share how you can reproduce the
issue?
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: Show control files in cgroup2 root after mount
Date: Tue, 18 Jul 2017 16:12:29 -0400 [thread overview]
Message-ID: <20170718201229.GD3365493@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <539870d2-8b85-2f54-61bd-4ba068e75ce0@redhat.com>
Hello,
On Tue, Jul 18, 2017 at 04:00:45PM -0400, Waiman Long wrote:
> From my own debugging, the controller files (e.g. the debug controller)
> were indirectly populated by the rebind_subsystems() call.
>
> [ 1.628103] css_populate_dir: init subsystem debug
...
> [ 1.654975] cgroup_apply_control_enable+0x103/0x340
> [ 1.657719] cgroup_apply_control+0x1a/0x30
> [ 1.658521] rebind_subsystems+0x18a/0x3b0
...
But there's kernfs_activate() call at the end of rebind_subsystems(),
so if the files were being added there, it should have been activated
there and I can confirm that the files are correctly added / removed
from the cgroup2 root directory when controllers are attached to /
detached from it.
> For the default cgroup2 root, kernfs_activate() was only called at the
> beginning in cgroup_init() with only the base cgroup files added. No
> more call after that until I touched the cgroup.subtree_control file.
Hmm... we're activating at the end of
* cgroup_setup_root()
* rebind_subsystems()
* cgroup_subtree_control_write()
* cgroup_apply_cftypes() after successful addition
* cgroup_mkdir()
I *think* this should cover everything. Just in case, are you looking
at the mainline kernel? Can you share how you can reproduce the
issue?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-07-18 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 19:32 [PATCH] cgroup: Show control files in cgroup2 root after mount Waiman Long
2017-07-18 19:32 ` Waiman Long
[not found] ` <1500406336-29512-1-git-send-email-longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 19:51 ` Tejun Heo
2017-07-18 19:51 ` Tejun Heo
[not found] ` <20170718195148.GC3365493-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2017-07-18 20:00 ` Waiman Long
2017-07-18 20:00 ` Waiman Long
[not found] ` <539870d2-8b85-2f54-61bd-4ba068e75ce0-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 20:12 ` Tejun Heo [this message]
2017-07-18 20:12 ` Tejun Heo
2017-07-18 20:29 ` Waiman Long
[not found] ` <255cc198-2c10-af76-98ca-086807d11540-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 20:50 ` Tejun Heo
2017-07-18 20:50 ` Tejun Heo
2017-07-18 21:06 ` Tejun Heo
2017-07-18 21:57 ` [PATCH cgroup/for-4.13-fixes] cgroup: create dfl_root files on subsys registration Tejun Heo
[not found] ` <20170718215746.GG3365493-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2017-07-18 22:09 ` Waiman Long
2017-07-18 22:09 ` Waiman Long
[not found] ` <d44b7b53-0be6-7019-169a-aa45b4d02598-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-07-18 22:11 ` Tejun Heo
2017-07-18 22:11 ` 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=20170718201229.GD3365493@devbig577.frc2.facebook.com \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=longman-H+wXaHxf7aLQT0dZR+AlfA@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.