aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorDarren Hart <dvhltc@us.ibm.com>2009-10-15 15:30:48 -0700
committerIngo Molnar <mingo@elte.hu>2009-10-16 10:19:18 +0200
commit89061d3d58e1f0742139605dc6a7950aa1ecc019 (patch)
tree4bf78b9d0834975b6e615ced614c74c67d57d52d /Documentation
parent237c80c5c8fb7ec128cf2a756b550dc41ad7eac7 (diff)
downloadkernel_samsung_smdk4412-89061d3d58e1f0742139605dc6a7950aa1ecc019.zip
kernel_samsung_smdk4412-89061d3d58e1f0742139605dc6a7950aa1ecc019.tar.gz
kernel_samsung_smdk4412-89061d3d58e1f0742139605dc6a7950aa1ecc019.tar.bz2
futex: Move drop_futex_key_refs out of spinlock'ed region
When requeuing tasks from one futex to another, the reference held by the requeued task to the original futex location needs to be dropped eventually. Dropping the reference may ultimately lead to a call to "iput_final" and subsequently call into filesystem- specific code - which may be non-atomic. It is therefore safer to defer this drop operation until after the futex_hash_bucket spinlock has been dropped. Originally-From: Helge Bahmann <hcb@chaoticmind.net> Signed-off-by: Darren Hart <dvhltc@us.ibm.com> Cc: <stable@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Eric Dumazet <eric.dumazet@gmail.com> Cc: Dinakar Guniguntala <dino@in.ibm.com> Cc: John Stultz <johnstul@linux.vnet.ibm.com> Cc: Sven-Thorsten Dietrich <sdietrich@novell.com> Cc: John Kacur <jkacur@redhat.com> LKML-Reference: <4AD7A298.5040802@us.ibm.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions