diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-09-27 16:45:33 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-09-27 16:45:33 -0700 |
commit | 6111da3432b10b2c56a21a5d8671aee46435326d (patch) | |
tree | dc85fcc0b58ab24754367794c5b617117afce734 /scripts/bloat-o-meter | |
parent | 83692898642a6d4950d3cd47971b101424d47859 (diff) | |
parent | 2ad654bc5e2b211e92f66da1d819e47d79a866f0 (diff) | |
download | op-kernel-dev-6111da3432b10b2c56a21a5d8671aee46435326d.zip op-kernel-dev-6111da3432b10b2c56a21a5d8671aee46435326d.tar.gz |
Merge branch 'for-3.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
Pull cgroup fixes from Tejun Heo:
"This is quite late but these need to be backported anyway.
This is the fix for a long-standing cpuset bug which existed from
2009. cpuset makes use of PF_SPREAD_{PAGE|SLAB} flags to modify the
task's memory allocation behavior according to the settings of the
cpuset it belongs to; unfortunately, when those flags have to be
changed, cpuset did so directly even whlie the target task is running,
which is obviously racy as task->flags may be modified by the task
itself at any time. This obscure bug manifested as corrupt
PF_USED_MATH flag leading to a weird crash.
The bug is fixed by moving the flag to task->atomic_flags. The first
two are prepatory ones to help defining atomic_flags accessors and the
third one is the actual fix"
* 'for-3.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
cpuset: PF_SPREAD_PAGE and PF_SPREAD_SLAB should be atomic flags
sched: add macros to define bitops for task atomic flags
sched: fix confusing PFA_NO_NEW_PRIVS constant
Diffstat (limited to 'scripts/bloat-o-meter')
0 files changed, 0 insertions, 0 deletions