From 474b9e81550ff32b581ce9cc90159a51442bce92 Mon Sep 17 00:00:00 2001 From: Alex Ionescu Date: Sun, 20 Nov 2005 08:46:09 +0000 Subject: [PATCH] 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 --- reactos/drivers/fs/np/create.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/reactos/drivers/fs/np/create.c b/reactos/drivers/fs/np/create.c index 198b3d9a066..cb1510956c2 100644 --- a/reactos/drivers/fs/np/create.c +++ b/reactos/drivers/fs/np/create.c @@ -618,13 +618,13 @@ NpfsCleanup(PDEVICE_OBJECT DeviceObject, KeSetEvent(&OtherSide->WriteEvent, IO_NO_INCREMENT, FALSE); if (Server) { + ExReleaseFastMutex(&OtherSide->DataListLock); ExReleaseFastMutex(&Fcb->DataListLock); - ExReleaseFastMutex(&OtherSide->DataListLock); } else { - ExReleaseFastMutex(&OtherSide->DataListLock); - ExReleaseFastMutex(&Fcb->DataListLock); + ExReleaseFastMutex(&Fcb->DataListLock); + ExReleaseFastMutex(&OtherSide->DataListLock); } } else if (Fcb->PipeState == FILE_PIPE_LISTENING_STATE)