From 9f2587c3b307c3b964ead4c338cb8fcc8617bfff Mon Sep 17 00:00:00 2001
From: Olga Kornievskaia <aglo@citi.umich.edu>
Date: Wed, 22 Jun 2011 11:42:30 -0400
Subject: [PATCH] [driver] abandoned upcalls dont delete security context

Deleting client's security context was causing kernel crashes.

During upcall, we remember a pointer to the client's security context,
then on close we delete the security context. Previously we would also
delete the context if the upcall was abandoned.

Apparently, windows will always send a close for the fcb that was used
for the abandoned upcall. Close deletes the context. Then when upcall
was done, it would try to delete the context again (oops).
---
 sys/nfs41_driver.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sys/nfs41_driver.c b/sys/nfs41_driver.c
index 4c2c73a..d036989 100644
--- a/sys/nfs41_driver.c
+++ b/sys/nfs41_driver.c
@@ -1423,7 +1423,6 @@ nfs41_downcall (
             print_error("[downcall] Nobody is waiting for this request!!!\n");
             ExReleaseFastMutex(&cur->lock);
             nfs41_RemoveEntry(downcallLock, downcall, cur);
-            SeDeleteClientSecurity(cur->psec_ctx);
             RxFreePool(cur);
             status = STATUS_UNSUCCESSFUL;
             goto out_free;