Hi Sreekanth,
section "3.3.5.9.10 Handling the SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2 Create
Context" has following text
If the SMB2_DHANDLE_FLAG_PERSISTENT bit is set in the Flags field of the
request, TreeConnect.Share.IsCA is TRUE, and Connection.ServerCapabilities
includes SMB2_GLOBAL_CAP_PERSISTENT_HANDLES, the server MUST set
Open.IsPersistent to TRUE
We clearly see that establishing durable handle as per sections
3.2.4.28/3.2.4.29 (from Question 8) cannot disregard
SMB2_GLOBAL_CAP_PERSISTENT_HANDLES. So it is necessary to have both
SMB2_GLOBAL_CAP_PERSISTENT_HANDLES and SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY
(which sets .IsCA property of network share)
If you think I misunderstood your question, please clarify.
Question 8:
The impact of SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY without
SMB2_GLOBAL_CAP_PERSISTENT_HANDLES is a very important part of this.
I guess this related to Question 6.
I guess we can close Question 8.
Thanks!
metze
_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
