Clipper locking

Christopher R. Hertel crh at
Tue Jun 13 22:58:51 GMT 2000

I think that's it, Mike.  At the CIFS conference there was some issue with
overlapping byte range locking in opportunistic locks.  I don't have specifics
but it was being worked on.  On the plus side, the new tools that Tridge has
been building for testing these things should help find these bugs sooner, and
not just in Samba code but in many third-party vendor's code.

Chris -)-----

On Jun 14,  8:28am, Allen, Michael B (RSCH) wrote:
> Subject: RE: Clipper locking
> > -----Original Message-----
> > From:	Elvis Pfutzenreuter [SMTP:epx at]
> >
> > So Windows or Samba is caching something when it shouldn't.
> 	[Allen, Michael B (RSCH)]
> 	I don't know much about the internals of Samba but I've been looking
> at the specification enough to know that this sounds like maybe a
> concurrency issue with the byte range locking implementation. Opportunistic
> locks come to mind too but thats only about caching on the client side.
> 	What you might consider doing is if the error is easily
> reproducible, set up the Ethereal packet sniffer and compare the offending
> operation to it's successful windows counterpart.
> 	My 2 cents,
> 	Michael B. Allen
>-- End of excerpt from Allen, Michael B (RSCH)

Christopher R. Hertel -)-----                   University of Minnesota
crh at              Networking and Telecommunications Services

More information about the samba-technical mailing list