Re: Re: file locking
Jeffrey Altman <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Organization | No Longer Affiliated with Columbia University in the City of New York |
| Message-ID | <[email protected]> |
It appears that the problems with byte-range locks in the existing
SMB/CIFS client are two-fold:
(1) the ReceiveV3LockingX function intentionlly ignores any request
for a lock whose offset does not equal zero and whose length is
not the size of the file
(2) the cm_scache_t object contains a lock queue but the cm_Lock
function does nothing to attempt to manage lock ranges. Any
lock that exists will result in subsequent non-overlapping locks
failing with a CM_ERROR_WOULDBLOCK error.
It seems clear to me that cm_Lock and cm_Unlock need to be fixed both
for the use of the SMB/CIFS client but also if the IFS client wants to
be able to use them.
Jeffrey Altman
smime.p7s
(application/x-pkcs7-signature, 3.2 KB) - not displayed