[cifs-protocol] [REG:114111212024789] Handling SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 Create Context

Bryan Burgin bburgin at microsoft.com
Wed Nov 12 10:27:07 MST 2014


[Dochelp to bcc]
[+casemail]

Hi Anubhav,

Thank you for your question.  We created SR 114111212024789 to track this.  An engineer will contact you soon.

Bryan

From: Anubhav Rakshit [mailto:anubhav.rakshit at gmail.com]
Sent: Wednesday, November 12, 2014 12:58 AM
To: Interoperability Documentation Help
Cc: cifs-protocol at samba.org
Subject: Handling SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 Create Context


With reference to MS-SMB2  v20140502 section 3.3.5.9.10 I am trying to test the following scenario as mentioned in the specs:

If an Open is found and the SMB2_FLAGS_REPLAY_OPERATION bit is not set in the SMB2 header,
the server MUST fail the request with STATUS_DUPLICATE_OBJECTID.



I have two test cases. In one of the test cases, I get the expected error STATUS_DUPLICATE_OBJECTID and in the other I get STATUS_SUCCESS.



Case 1:
1.    Send SMB2_CREATE request with SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 context to server. This call succeeds.
2.    Re-send the exact same request as above and the server fails the request with STATUS_DUPLICATE_OBJECTID. Also the server sends an Oplock break notification.

Case 2:
1.    Send SMB2_CREATE request with SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 context to server. This call succeeds.
2.    Send SMB2_QUERY_INFO on the above File Handle. This call succeeds.
3.    Re-send the exact same request as 1. We see an Oplock break notification triggered. Also the SMB2_CREATE succeeds.

According to the specs SMB2_CREATE in 3. should have failed with STATUS_DUPLICATE_OBJECTID. Can you please explain why the server behaves differently in this case?



I am also attaching the Message Analyzer captures for both the cases. For Case 1. look at "duplicate_objectid_pass" Frame 3444. For Case 2. look at "duplicate_objectid_fail" Frame 45.



Thanks,

anubhav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20141112/896e80b4/attachment.html>


More information about the cifs-protocol mailing list