diff options
| author |   Linus Torvalds <torvalds@linux-foundation.org> | 2016-02-10 11:36:19 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-02-10 11:36:19 -0800 |
| commit | fb0dc5f129bc2d4763bdc237b8df0e1708c03e1e (patch) | |
| tree | 4c635f1ca11535c0072d2f10282a31d16979d639 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | Merge branch 'for-4.5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq (diff) | |
| parent | Documentation: cgroup: Fix 'cgroup-legacy' -> 'cgroup-v1' (diff) | |
| download | linux-rng-fb0dc5f129bc2d4763bdc237b8df0e1708c03e1e.tar.xz linux-rng-fb0dc5f129bc2d4763bdc237b8df0e1708c03e1e.zip | |
Merge branch 'for-4.5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
Pull cgroup fixes from Tejun Heo:
- The destruction path of cgroup objects are asynchronous and
multi-staged and some of them ended up destroying parents before
children leading to failures in cpu and memory controllers. Ensure
that parents are always destroyed after children.
- cpuset mm node migration was performed synchronously while holding
threadgroup and cgroup mutexes and the recent threadgroup locking
update resulted in a possible deadlock. The migration is best effort
and shouldn't have been performed under those locks to begin with.
Made asynchronous.
- Minor documentation fix.
* 'for-4.5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
Documentation: cgroup: Fix 'cgroup-legacy' -> 'cgroup-v1'
cgroup: make sure a parent css isn't freed before its children
cgroup: make sure a parent css isn't offlined before its children
cpuset: make mm migration asynchronous
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions