From: Jeffrey Altman <jaltman@your-file-system.com>
Date: Thu, 7 Mar 2013 05:56:15 +0000 (-0500)
Subject: Windows: Claim success for Delete Reparse Tag
X-Git-Tag: openafs-stable-1_8_0pre1~1316
X-Git-Url: http://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=abbee864c48fb2e439c4141130ada184fad23db5

Windows: Claim success for Delete Reparse Tag

The typical pattern for deleting a reparse point is

 1. open reparse point object
 2. delete reparse tag
 3. set delete on close
 4. close handle

Claim success when we receive delete reparse tag fsctl so that
the delete on close disposition can be set.

Change-Id: I8f4212dd6ba04be95455eaa210e632ca59cfa7c8
Reviewed-on: http://gerrit.openafs.org/9427
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
Tested-by: Jeffrey Altman <jaltman@your-file-system.com>
---

diff --git a/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp b/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp
index 77c691f..d8a9d22 100644
--- a/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp
+++ b/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp
@@ -848,10 +848,12 @@ AFSProcessUserFsRequest( IN PIRP Irp)
                 }
 
                 //
-                // For now deny access on this call
+                // Claim success.  The typical usage is setting delete on close
+                // as the next operation on the reparse point before closing
+                // the handle.
                 //
 
-                ntStatus = STATUS_ACCESS_DENIED;
+                ntStatus = STATUS_SUCCESS;
 
                 break;
             }