Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS

[Jeremy Allison]

On Fri, May 24, 2002 at 10:26:00PM -0400, Richard Bollinger wrote:
> Right... or if it times out because of the dead time setting... so it's shouldn't be that rare
> in the wild.  I have a feeling that a lot of folks just disable oplocks to avoid the "troubles".
> My test at work showed that the problem did not occur with a W2K server when I forced the
> disconnect from the server end.

Well, I've managed to get this to happen to a W2K server too,
took me a while though.....

It's definately a client bug with the Win9x client, but we seem
to trigger it all the time whereas Win2k seems to trigger it sometimes.

I've also finally got a trace where a W2K server resends an oplock
break twice, after 300ms - this must be their magic timeout to wake
up the client.

This is *extremely* interesting. I'm cc:ing this to tridge directly,
in case he doesn't believe me :-) :-).

There are definately some subtle heuristics in play here - on my
vmware W2k server it doesn't seem to grant oplocks to the Win9x
client after the restart - on my "real" win2k server it does.

I need to play with this more and understand it (lucky it's a
long weekend :-) :-).

Jeremy.