summaryrefslogtreecommitdiffstats
path: root/net/xfrm/Kconfig
diff options
context:
space:
mode:
authorJens Axboe <jens.axboe@oracle.com>2007-09-13 14:26:53 +0200
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-09-13 08:20:25 -0700
commitf3da54ba140c6427fa4a32913e1bf406f41b5dda (patch)
treee39f3c21a06abbf23944e03fc5ec422fc434fc00 /net/xfrm/Kconfig
parent9ca2152e173554e7ffb7919dc4916a7c61f8be1a (diff)
downloadkernel-crypto-f3da54ba140c6427fa4a32913e1bf406f41b5dda.tar.gz
kernel-crypto-f3da54ba140c6427fa4a32913e1bf406f41b5dda.tar.xz
kernel-crypto-f3da54ba140c6427fa4a32913e1bf406f41b5dda.zip
Fix race with shared tag queue maps
There's a race condition in blk_queue_end_tag() for shared tag maps, users include stex (promise supertrak thingy) and qla2xxx. The former at least has reported bugs in this area, not sure why we haven't seen any for the latter. It could be because the window is narrow and that other conditions in the qla2xxx code hide this. It's a real bug, though, as the stex smp users can attest. We need to ensure two things - the tag bit clearing needs to happen AFTER we cleared the tag pointer, as the tag bit clearing/setting is what protects this map. Secondly, we need to ensure that the visibility of the tag pointer and tag bit clear are ordered properly. [ I removed the SMP barriers - "test_and_clear_bit()" already implies all the required barriers. -- Linus ] Also see http://bugzilla.kernel.org/show_bug.cgi?id=7842 Signed-off-by: Jens Axboe <jens.axboe@oracle.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'net/xfrm/Kconfig')
0 files changed, 0 insertions, 0 deletions