mirror of
https://github.com/reactos/reactos.git
synced 2024-07-06 12:45:16 +00:00
It is generally considered a good idea to release a fast mutex in the same order that you acquired it, since acquiring at passive->apc and apc->apc does not bode well when you release to apc->passive. passive->apc. This fixes the npfs bug on vmware, lowering the total npfs bug count to a mere 42.
svn path=/trunk/; revision=19357
This commit is contained in:
parent
4c62f96aad
commit
474b9e8155
|
@ -618,13 +618,13 @@ NpfsCleanup(PDEVICE_OBJECT DeviceObject,
|
|||
KeSetEvent(&OtherSide->WriteEvent, IO_NO_INCREMENT, FALSE);
|
||||
if (Server)
|
||||
{
|
||||
ExReleaseFastMutex(&Fcb->DataListLock);
|
||||
ExReleaseFastMutex(&OtherSide->DataListLock);
|
||||
ExReleaseFastMutex(&Fcb->DataListLock);
|
||||
}
|
||||
else
|
||||
{
|
||||
ExReleaseFastMutex(&OtherSide->DataListLock);
|
||||
ExReleaseFastMutex(&Fcb->DataListLock);
|
||||
ExReleaseFastMutex(&OtherSide->DataListLock);
|
||||
}
|
||||
}
|
||||
else if (Fcb->PipeState == FILE_PIPE_LISTENING_STATE)
|
||||
|
|
Loading…
Reference in a new issue