[PATCH][SAMBA3] use implicit oplocks to allow write caching

Jeremy Allison jra at samba.org
Thu Mar 23 00:23:04 GMT 2006

On Mon, Mar 20, 2006 at 11:35:19AM +1100, James Peach wrote:
> Hi all,
> The attached patch introduces a new IMPLICIT_OPLOCK modifier to standard
> exclusive oplocks. The purpose of this is to allow write caching support
> in the presence of CIFS clients that do not use oplocks.
> An implicit oplock is an exclusive oplock that is taken without the
> knowledge of the CIFS client. This means that when the oplock is broken,
> the client must not be notified. Other than that, there is no change to
> either the oplock implementation or semantics.
> Any a write cache that was established while an exclusive oplock was
> if force is removed once the oplock is broken.
> Jeremy and Volker, can you please cast an eye over this?

Ok, don't check this in yet please. I need to look over the implications
of adding a new type flag into the share mode db. The last oplock logic
bug was due to all possible type flags not being checked, so I really
want to invesitgate all the places we go over the entries first.

Give me a few days....


More information about the samba-technical mailing list