summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2016-01-21 15:32:15 -0500
committerRunmin Wang <runminw@codeaurora.org>2016-09-09 15:01:53 -0700
commitbeb35bfaa554d20ba08243a28ebfdd24e644b502 (patch)
treefbaea19e7b993edde04c2df3dd08b8e274e385ef /tools/perf/scripts/python/bin
parent3dc7ca5e82cc56abc0463e35f1851cd8e2eed97a (diff)
cgroup: make sure a parent css isn't freed before its children
commit 8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4 upstream. 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. Change-Id: I97febdd414ef5cd57490ce2746650dde7fdda28f Signed-off-by: Tejun Heo <tj@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org>i Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Git-commit: 8bb5ef79bc0f4016ecf79e8dce6096a3c63603e4 Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Signed-off-by: Runmin Wang <runminw@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions