diff options
| author | Oleg Nesterov <[email protected]> | 2010-03-15 10:10:23 +0100 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2010-04-02 20:12:03 +0200 |
| commit | 6a1bdc1b577ebcb65f6603c57f8347309bc4ab13 (patch) | |
| tree | 516130eedf782dd14505bd111e06bcfad9923b07 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 30da688ef6b76e01969b00608202fff1eed2accc (diff) | |
sched: _cpu_down(): Don't play with current->cpus_allowed
_cpu_down() changes the current task's affinity and then recovers it at
the end. The problems are well known: we can't restore old_allowed if it
was bound to the now-dead-cpu, and we can race with the userspace which
can change cpu-affinity during unplug.
_cpu_down() should not play with current->cpus_allowed at all. Instead,
take_cpu_down() can migrate the caller of _cpu_down() after __cpu_disable()
removes the dying cpu from cpu_online_mask.
Signed-off-by: Oleg Nesterov <[email protected]>
Acked-by: Rafael J. Wysocki <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
LKML-Reference: <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions