diff options
| author | Volker Lendecke <vl@samba.org> | 2010-10-02 17:07:00 +0200 |
|---|---|---|
| committer | Karolin Seeger <kseeger@samba.org> | 2011-01-13 17:58:51 +0100 |
| commit | fc80176d53a35c5e0d188c82f3cc301106c87671 (patch) | |
| tree | 9d50e122a30b51f109e4fbac8f2a94974ce3ca78 | |
| parent | e3e35faada0c5baa40d4b3b67341cb30a66233cd (diff) | |
| download | samba-fc80176d53a35c5e0d188c82f3cc301106c87671.tar.gz | |
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)
(cherry picked from commit e18ef6cdf042a73e7f08b792e4a9901b071b1f67)
| -rw-r--r-- | source3/smbd/oplock.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/source3/smbd/oplock.c b/source3/smbd/oplock.c index 086ce1ac23e..e690276b277 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); } |