[OpenAFS] Re: safe+portable way to determine if byte-range-locking is dangerous?

Adam Megacz megacz@cs.berkeley.edu
Sat, 16 Dec 2006 08:57:00 -0800

Jeffrey Altman <jaltman@secure-endpoints.com> writes:
> There is nothing wrong with a client grabbing a full file lock on behalf
> of an application when the application requests a lock on a subset of
> the range provided that the client is capable of managing all of the
> byte range allocations locally.
> ...
> What is dangerous is when a request for a byte-range lock succeeds
> when no lock on the file is actually obtained from the file server.

I agree 100%.

  - a

PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380