locking 2.0.7 -> 2.2.2

[Matthew Geddes]

Hi all,

I have a client that upgraded from 2.0.x to 2.2.2 and is having a fairly 
regular locking problem where two client applications (some FoxPro DB on 
a share) stop responding to user input. Sometimes killing one brings the 
other one back. So my questions are:

Are there any known issues with locking in 2.2.2 on a 2.2.14 kernel 
Linux box?

Is it likely to be something to do with the lack of kernel oplock 
support in the 2.2.x series kernels?

Was there much difference in the locking internals between Samba 2.0.x 
and Samba 2.2.2?

thx,
Matt