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

[Jeremy Allison]

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.

This code works perfectly on my local systems and
also on sn-devel, so I think it's the kernel you
have that's a fault here.

If you can RB+ my patch, I'll push it to master
as at least it means that the tests don't hang
anymore and you can track down what's wrong in
your test env without carrying an extra patch.

(This patch would be good to have in master anyway,
as it prevents any hanging if the tests are being
run on a broken Linux kernel).

Cheers,

	Jeremy.