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

[Jeremy Allison]

On Thu, Nov 16, 2017 at 07:52:29AM +1300, Gary Lockyer wrote:
> 
> 
> On 16/11/17 07:06, Jeremy Allison via samba-technical wrote:
> > On Thu, Nov 16, 2017 at 06:55:13AM +1300, Gary Lockyer via samba-technical wrote:
> >> I'm now seeing significant numbers of builds hanging in:
> >>
> >> [558(3538)/2212 at 1h13m33s] samba3.smb2.kernel-oplocks(nt4_dc)
> > 
> > Can you track down what part of the test it's hanging in ?
> > A strace on the smbtorture client process would help here.
> I'll kick off some builds now, and see what I can find.
> > 
> > The test does depend on working kernel oplocks as the
> > test child holds the lease for 3 seconds. Also, the
> > child does a pause() waiting for a signal which is
> > expected to come when the smbd tries to open the leased
> > file. I could add a 5 second alarm() timeout to ensure
> > it can't ever hang there but under normal circumstances
> > it shouldn't hang.
> > 
> > What platform are you testing on - if it's non-Linux
> > this test should not be running.
> Ubuntu 14.04

I'm also developing and testing on a variant of 14.04,
so the kernel should work.

I'm running with kernel 4.4.0-93-generic. What kernel
version is on yours ?