From abbee864c48fb2e439c4141130ada184fad23db5 Mon Sep 17 00:00:00 2001 From: Jeffrey Altman Date: Thu, 7 Mar 2013 00:56:15 -0500 Subject: [PATCH] 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 Reviewed-by: Jeffrey Altman Tested-by: Jeffrey Altman --- src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp b/src/WINNT/afsrdr/kernel/lib/AFSFSControl.cpp index 77c691ffe..d8a9d223f 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; } -- 2.39.5