[mjmartin] 38638: - Don't call KeWaitForSingleObject here, as doing so can lock the thread in a wait if no one ever connects to it. Also the wait is handled in Kernel32.

Author: mjmartin
Date: Thu Jan  8 01:45:42 2009
New Revision: 38638

URL: http://svn.reactos.org/svn/reactos?rev=38638&view=rev
Log:
- Don't call KeWaitForSingleObject here, as doing so can lock the thread in a wait if
no one ever connects to it. Also the wait is handled in Kernel32.

Modified:
    trunk/reactos/drivers/filesystems/npfs/fsctrl.c

Modified: trunk/reactos/drivers/filesystems/npfs/fsctrl.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/filesystems/npfs/f…
==============================================================================
--- trunk/reactos/drivers/filesystems/npfs/fsctrl.c [iso-8859-1] (original)
+++ trunk/reactos/drivers/filesystems/npfs/fsctrl.c [iso-8859-1] Thu Jan  8 01:45:42 2009
@@ -167,11 +167,8 @@
 
 	if (Flags & FO_SYNCHRONOUS_IO)
 	{
-		KeWaitForSingleObject(&Ccb->ConnectEvent,
-			UserRequest,
-			KernelMode,
-			FALSE,
-			NULL);
+		IoMarkIrpPending(Irp);
+		Status = STATUS_PENDING;
 	}
 
 	DPRINT("NpfsConnectPipe() done (Status %lx)\n", Status);