An oplock break reply from the client causes the sequence number to be
authorJeremy Allison <jra@samba.org>
Thu, 7 Aug 2003 05:36:08 +0000 (05:36 +0000)
committerJeremy Allison <jra@samba.org>
Thu, 7 Aug 2003 05:36:08 +0000 (05:36 +0000)
commit3bbe9c0869ea8653f684afa9a1345f6fa2f80b4b
tree9a6a6e119b868063e7f998cb7b36afb07af01570
parenta3513090e77ddf380f7de67fc625e15ad16d5e4b
An oplock break reply from the client causes the sequence number to be
updated by 2 if there is no open reply outstanding, else by one....
Yes - this makes no sense....
Jeremy.
(This used to be commit b43ce1ff6109f6422a621329ceb713b42df40040)
source3/libsmb/smb_signing.c
source3/smbd/open.c
source3/smbd/oplock.c