[cifs-protocol] SMB3 channel sequence

Stefan (metze) Metzmacher metze at samba.org
Tue Aug 7 20:21:21 MDT 2012

Hi DocHelp,

I have some questions regarding the channel sequence verification
of SMB 3.00.

- When is Open.OutstandingPreRequestCount supposed to be decremented or

- What happens on an 16-bit overflow?
  From the documentation it looks like, the server would
  always reject write/ioctl/setinfo with STATUS_FILE_NOT_AVAILABLE
  once the channel sequence wrapped.

- As the client maintains the channel sequence on the session,
  while the server maintains it on the open, it seems not to be
  unlikely that the values get out of sync.
  (Assuming there's a way to handle the general 16-bit overflow)
  It could happen that the client opened a file and doesn't
  use the handle for a long time (while the 16-bit value got an overflow
  on the client). This would mean that the server can know if
  a channel sequence is older or newer than the last one.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20120808/16db7b06/attachment.pgp>

More information about the cifs-protocol mailing list