client-omit-zero-length-reads-20050804

The attached patch restores the behaviour of the 1.2.x client: writes
appending to a file do not trigger a 0-length read which at best updates the
current status. If another cache manager wrote to the same file in the
meantime, the file status is updated only after the StoreData RPC (and for
the changes the last one wins).

diff --git a/src/afs/afs_dcache.c b/src/afs/afs_dcache.c
index c77002e2e3b94cb09304adddea77fe19d4db72ca..cf4cef70a43f438afa85505986069d0fc97f7c89 100644 (file)
--- a/src/afs/afs_dcache.c
+++ b/src/afs/afs_dcache.c
@@ -1967,7 +1967,7 @@ afs_GetDCache(register struct vcache *avc, afs_size_t abyte,
     if ((aflags & 4) && (hiszero(avc->m.DataVersion)))
        doAdjustSize = 1;
     if ((AFS_CHUNKTOBASE(chunk) >= avc->m.Length) ||
-        ((aflags & 4) && (abyte == Position) && (tlen >= size))))
+        ((aflags & 4) && (abyte == Position) && (tlen >= size)))
        overWriteWholeChunk = 1;
     if (doAdjustSize || overWriteWholeChunk) {
 #if    defined(AFS_AIX32_ENV) || defined(AFS_SGI_ENV)