[PATCH] Fix bug #13121 - Non-smbd processes using kernel oplocks can hang smbd

[Andrew Bartlett]

On Wed, 2017-11-15 at 13:29 -0800, Jeremy Allison via samba-technical
wrote:
> On Thu, Nov 16, 2017 at 10:18:26AM +1300, Gary Lockyer wrote:
> 
> > Ok just failed logs attached.
> > [558(3552)/2212 at 1h9m32s] samba3.smb2.kernel-oplocks(nt4_dc)
> > Bad child exit code 10
> 
> Right - the key is the above. It comes from here in my new
> patch:
> 
> +       if (got_alarm == 1) {
> +               return 10;
> +       }
> 
> which means that the alarm(5) is firing in the client.
> 
> This means your kernel is not sending a RT_SIGNAL_LEASE
> signal correctly to the client process holding the lease.
> 
> AKA - you're running with a broken kernel.

I've just worked with Gary to use a more recent 14.04 image for the
cloud builds, that should clear this up.

Andrew Bartlett

-- 
Andrew Bartlett
https://samba.org/~abartlet/
Authentication Developer, Samba Team         https://samba.org
Samba Development and Support, Catalyst IT   
https://catalyst.net.nz/services/samba