> a note about how "OpLock" means the same as "opportunistic lock"
This one is a bit silly, I admit, but consider this one:
> Note: Your application should not perform any file system operations on the file between [calling CreateFile2] and [requesting an oplock]. Doing so may cause deadlocks.
This one is a bit silly, I admit, but consider this one:
> Note: Your application should not perform any file system operations on the file between [calling CreateFile2] and [requesting an oplock]. Doing so may cause deadlocks.