- More fixes to pushlock implementation:
authorAleksey Bragin <aleksey@reactos.org>
Wed, 18 Jun 2008 11:34:10 +0000 (11:34 +0000)
committerAleksey Bragin <aleksey@reactos.org>
Wed, 18 Jun 2008 11:34:10 +0000 (11:34 +0000)
commitab2b63b87b8c56cba3812f6b8e36e06cfde39f25
tree0b229d905166b6ecc904ae848496b7e33e0d68d0
parent67572c740e6930a4ee94326e7952aa31e7086a54
- More fixes to pushlock implementation:
* In ExTimedWaitForUnblockPushLock, check only for STATUS_SUCCESS (which is the only status return when the wait was satisfied, while other like STATUS_TIMEOUT would still be considered a success).
* In ExBlockPushlock, fix a typo when trying out an interlocked exchange with a new value - wrong value was assigned.
* In ExfAcquirePushLockShared, assign PushLock value passed to this function, not the NewValue, like it's done in ExfAcquirePushLockExclusive.
* In ExfReleaseReleasePushLockExclusive, fix a typo which led to incorrect behavior and not waking up the pushlock when it should be.

svn path=/trunk/; revision=34008
reactos/ntoskrnl/ex/pushlock.c