Fix FileLockIntrinsic to propagate the exclusivity flag

The exclusivity flag determines whether we ask for an exclusive
lock or a read-shared lock.  We had neglected to initialize it.

Signed-off-by: Dmitry Torokhov <dtor@vmware.com>

diff --git a/open-vm-tools/lib/file/fileLockPrimitive.c b/open-vm-tools/lib/file/fileLockPrimitive.c
index 3a6c56664cc087ead853ec826741823b348273ec..5ba7de0d2b6cd79ff027eb09157b047ae56c4c33 100644 (file)
--- a/open-vm-tools/lib/file/fileLockPrimitive.c
+++ b/open-vm-tools/lib/file/fileLockPrimitive.c
@@ -1833,6 +1833,7 @@ FileLockIntrinsic(ConstUnicode pathName,   // IN:
    lockBase = Unicode_Append(pathName, FILELOCK_SUFFIX);
 
    myValues.lockType = exclusivity ? LOCK_EXCLUSIVE : LOCK_SHARED;
+   myValues.exclusivity = exclusivity;
    myValues.waitTime = 0;
    myValues.msecMaxWaitTime = msecMaxWaitTime;