Hi DocHelp, I have some questions regarding the channel sequence verification of SMB 3.00.
- When is Open.OutstandingPreRequestCount supposed to be decremented or reset? - 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. metze
signature.asc
Description: OpenPGP digital signature
_______________________________________________ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
