After talking with Microsoft engineers, immediately replying

on compound requests on open being deferred for a sharing violation
is a Windows bug. Re-enable the code that simply delays the compound
response if the delay time is less than 2 seconds.

Jeremy.

diff --git a/source3/smbd/smb2_create.c b/source3/smbd/smb2_create.c
index 65022d5c840cc3a6ff4d4a1e4fd7cd4b1ca09e67..09bd827802dae8f536a0de9ffc63c74473355231 100644 (file)
--- a/source3/smbd/smb2_create.c
+++ b/source3/smbd/smb2_create.c
@@ -1159,7 +1159,8 @@ bool push_deferred_open_message_smb2(struct smbd_smb2_request *smb2req,
        if (!state->private_data.data) {
                return false;
        }
-#if 0
+
+#if 1
        /* Boo - turns out this isn't what W2K8R2
           does. It actually sends the STATUS_PENDING
           message followed by the STATUS_SHARING_VIOLATION
@@ -1167,6 +1168,10 @@ bool push_deferred_open_message_smb2(struct smbd_smb2_request *smb2req,
           calls (even on directories) will potentially
           fail in a chain.... ? And I've seen directory
           opens as the start of a chain. JRA.
+
+          Update: 19th May 2010. Talking with Microsoft
+          engineers at the plugfest this is a bug in
+          Windows. Re-enable this code.
        */
        /*
         * More subtlety. To match W2K8R2 don't