The branch, v3-4-test has been updated via e18ef6c s3: Stop using the write cache after an oplock break from ead6726 WHATSNEW: Prepare 3.4.9 release notes.
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-4-test - Log ----------------------------------------------------------------- commit e18ef6cdf042a73e7f08b792e4a9901b071b1f67 Author: Volker Lendecke <v...@samba.org> Date: Sat Oct 2 17:07:00 2010 +0200 s3: Stop using the write cache after an oplock break Fix bug #7715 (Setting Samba Write Cache Size Can Cause File Corruption). (cherry picked from commit 9f8292e5f765dff586bfbb261b54da4d4b27a837) ----------------------------------------------------------------------- Summary of changes: source3/smbd/oplock.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Changeset truncated at 500 lines: diff --git a/source3/smbd/oplock.c b/source3/smbd/oplock.c index 086ce1a..e690276 100644 --- a/source3/smbd/oplock.c +++ b/source3/smbd/oplock.c @@ -118,6 +118,7 @@ void release_file_oplock(files_struct *fsp) fsp->sent_oplock_break = NO_BREAK_SENT; flush_write_cache(fsp, OPLOCK_RELEASE_FLUSH); + delete_write_cache(fsp); TALLOC_FREE(fsp->oplock_timeout); } -- Samba Shared Repository