diff options
author | Tejun Heo <tj@kernel.org> | 2016-01-21 23:32:15 +0300 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2016-01-22 18:42:58 +0300 |
commit | 8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4 (patch) | |
tree | 3a2129fd05443c134b033fd476f93ca0faf28b01 /Documentation/cgroup-v2.txt | |
parent | aa226ff4a1ce79f229c6b7a4c0a14e17fececd01 (diff) | |
download | linux-8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4.tar.xz |
cgroup: make sure a parent css isn't freed before its children
There are three subsystem callbacks in css shutdown path -
css_offline(), css_released() and css_free(). Except for
css_released(), cgroup core didn't guarantee the order of invocation.
css_offline() or css_free() could be called on a parent css before its
children. This behavior is unexpected and led to bugs in cpu and
memory controller.
The previous patch updated ordering for css_offline() which fixes the
cpu controller issue. While there currently isn't a known bug caused
by misordering of css_free() invocations, let's fix it too for
consistency.
css_free() ordering can be trivially fixed by moving putting of the
parent css below css_free() invocation.
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Diffstat (limited to 'Documentation/cgroup-v2.txt')
0 files changed, 0 insertions, 0 deletions