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)
committerJeremy Allison <jra@samba.org>
Tue, 5 Oct 2010 17:15:27 +0000 (10:15 -0700)
Autobuild-User: Volker Lendecke <vlendec@samba.org>
Autobuild-Date: Tue Oct  5 10:09:38 UTC 2010 on sn-devel-104
(cherry picked from commit ea08cd280cd03377cbabac8f6565719186330e44)

source3/smbd/oplock.c

index a878f36248703ca19dd6f8dc1288867d2fceb2f8..2348be47e1bc4c97ae199d25ef1e98847c9ec200 100644 (file)
@@ -119,6 +119,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);
 }