java-locking-redux-20070214

change the -1 len check for java locks slightly

diff --git a/src/afs/VNOPS/afs_vnop_flock.c b/src/afs/VNOPS/afs_vnop_flock.c
index 6b3b30ce94549c517af59ee1126cf957446a6fca..9d9f3842bc88e2fdf1f50a34ace43c5ae6b047fb 100644 (file)
--- a/src/afs/VNOPS/afs_vnop_flock.c
+++ b/src/afs/VNOPS/afs_vnop_flock.c
@@ -26,6 +26,10 @@ RCSID
 #include "afs/afs_osidnlc.h"
 #include "afs/unified_afs.h"
 
+#ifndef OFFSET_MAX
+#define OFFSET_MAX 0x7fffffffffffffff
+#endif
+
 /* Static prototypes */
 static int HandleGetLock(register struct vcache *avc,
                         register struct AFS_FLOCK *af,
@@ -549,7 +553,7 @@ int afs_lockctl(struct vcache * avc, struct AFS_FLOCK * af, int acmd,
 #endif
     /* Java VMs ask for l_len=(long)-1 regardless of OS/CPU; bottom 32 bits
      * sometimes get masked off by OS */
-    if ((af->l_len >> 32) == 0x7fffffff)
+    if (af->l_len == OFFSET_MAX-1)
        af->l_len = 0;
     /* next line makes byte range locks always succeed,
      * even when they should block */