Samba oplock level II problem

Pavel Shilovsky piastryyy at
Thu Feb 3 11:46:27 MST 2011

2011/2/1 Pavel Shilovsky <piastryyy at>:
> 2011/2/1 Jeremy Allison <jra at>:
>> On Tue, Feb 01, 2011 at 12:21:29AM +0300, Pavel Shilovsky wrote:
>>> >
>>> Please, look at the second variant of the patch - it has extra debug
>>> message if initial_break_processing returns NULL:
>> Got it - pushed (a similar patch) thanks !
> Today, I noticed that now we can have several fid with different
> oplock types in the same time. That's why we need to process
> conted_level2_oplocks_begin_default not only for level II current
> oplock type but for none oplock too (because another clients can have
> level II oplock to be broken in this call).
> So, I created the patch to fix it:
> --
> Best regards,
> Pavel Shilovsky.

What's about this patch? Is there any way to include these oplock
patches (this and two that were merged before) into the next bugfix
release of Samba-3.5.y?

Best regards,
Pavel Shilovsky.

More information about the samba-technical mailing list