diff options
author | Bharata B Rao <bharata@linux.vnet.ibm.com> | 2009-03-23 10:02:53 +0530 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-03-31 18:27:59 +0200 |
commit | a18b83b7ef3c98cd8b4bb885e4a649a8f30fb7b0 (patch) | |
tree | 4e93447c0099672e2bedbc4374007a42f105e132 /kernel/sched_cpupri.c | |
parent | 2f8501815256af8498904e68bd0984b1afffd6f8 (diff) | |
download | kernel_samsung_tuna-a18b83b7ef3c98cd8b4bb885e4a649a8f30fb7b0.zip kernel_samsung_tuna-a18b83b7ef3c98cd8b4bb885e4a649a8f30fb7b0.tar.gz kernel_samsung_tuna-a18b83b7ef3c98cd8b4bb885e4a649a8f30fb7b0.tar.bz2 |
cpuacct: make cpuacct hierarchy walk in cpuacct_charge() safe when rcupreempt is used -v2
Impact: fix cgroups race under rcu-preempt
cpuacct_charge() obtains task's ca and does a hierarchy walk upwards.
This can race with the task's movement between cgroups. This race
can cause an access to freed ca pointer in cpuacct_charge() or access
to invalid cgroups pointer of the task. This will not happen with rcu or
tree rcu as cpuacct_charge() is called with preemption disabled. However if
rcupreempt is used, the race is seen. Thanks to Li Zefan for explaining this.
Fix this race by explicitly protecting ca and the hierarchy walk with
rcu_read_lock().
Changes for v2:
- Update patch descrition (as per Li Zefan's review comments).
- Remove comments in cpuacct_charge() which explained why rcu_read_lock()
was needed (as per Peter Zijlstra's review comments).
Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>
Cc: Paul Menage <menage@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>
Tested-by: Balbir Singh <balbir@linux.vnet.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/sched_cpupri.c')
0 files changed, 0 insertions, 0 deletions