[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cifs-protocol
Subject:    [cifs-protocol] [MS-SMB2:2.2.1.x] SYNC vs. ASYNC commands.
From:       "Christopher R. Hertel" <crh () ubiqx ! mn ! org>
Date:       2013-11-15 20:20:07
Message-ID: 528681F7.8010502 () ubiqx ! mn ! org
[Download RAW message or body]

Dear Dochelp:

In [MS-SMB2], sections 2.2.1.1 and 2.2.1.2 both describe the Command field 
in the SMB2 header, and both give a complete list of all SMB2 commands.

Reading section 2.2.1, however, it seems that only the SMB2_CANCEL command 
uses the ASYNC header format, and that all others use the SYNC format.  If 
that interpretation is correct, then...

* In section 2.2.1.1, only SMB2_CANCEL should be listed as a valid command
   for the Command field.

* In section 2.2.1.2, SMB2_CANCEL should be excluded from the list of
   valid SYNC-format requests.

* Section 2.2.30 should indicate that the ASYNC header should be used
   instead of the SYNC header.

Am I misinterpreting the information in 2.2.1?  Please clarify the 
circumstances under which the ASYNC header format is used, vs. the SYNC format.

Thanks.

Chris -)-----

-- 
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh@ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh@ubiqx.org
_______________________________________________
cifs-protocol mailing list
cifs-protocol@samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
[prev in list] [next in list] [prev in thread] [next in thread]