s3: Stop using the write cache after an oplock break
authorVolker Lendecke <vl@samba.org>
Sat, 2 Oct 2010 15:07:00 +0000 (17:07 +0200)
committerVolker Lendecke <vl@samba.org>
Thu, 7 Oct 2010 08:27:28 +0000 (10:27 +0200)
commit92a2f80e19abdbcbc83bf8f55eae9c7cdfa538e2
tree1b5ef4e8b353a5743fbd9fdcf085829cc2cfc3d2
parente3aa5a62f28dd9ff4ace599ef9764ba76f12a65e
s3: Stop using the write cache after an oplock break

This fixes samba-bug 7715: If "write cache size" is set (a typical tuning knob
that might be applied in critical customer situations by performance experts),
smbd can corrupt data. This fixes it.
source3/smbd/oplock.c