summaryrefslogtreecommitdiff
path: root/Utility/LockPool/PidLock.hs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-03-01 15:31:39 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-03-01 15:31:39 -0400
commit59bb9730f6d245c2e917d048f2de3f5db3d00298 (patch)
treefe58da62730efc299bbc96d6f52af270c733f4dc /Utility/LockPool/PidLock.hs
parent784c3fa0139a5fc0ce459501d713cfe5c39d5a23 (diff)
Fix shared lock file FD leak.
This fixes behavior in this situation: l1 <- lockShared Nothing "lck" l2 <- lockShared Nothing "lck" dropLock l1 dropLock l2 Before, the lock was dropped upon the second dropLock call, but the fd remained open, and would never be closed while the program was running. Fixed by a rather round-about method, but it should work well enough. It would have been simpler to open open the shared lock once, and not open it again in the second call to lockShared. But, that's difficult to do atomically. This also affects Windows and PID locks, not just posix locks. In the case of pid locks, multiple calls to waitLock within the same process are allowed because the side lock is locked using a posix lock, and so multiple exclusive locks can be taken in the same process. So, this change fixes a similar problem with pid locks. l1 <- waitLock (Seconds 1) "lck" l2 <- waitLock (Seconds 1) "lck" dropLock l1 dropLock l2 Here the l2 side lock fd remained open but not locked, although the pid lock file was removed. After this change, the second dropLock will close both fds to the side lock, and delete the pidlock.
Diffstat (limited to 'Utility/LockPool/PidLock.hs')
-rw-r--r--Utility/LockPool/PidLock.hs12
1 files changed, 6 insertions, 6 deletions
diff --git a/Utility/LockPool/PidLock.hs b/Utility/LockPool/PidLock.hs
index 2b3ee67f9..26ed96f3c 100644
--- a/Utility/LockPool/PidLock.hs
+++ b/Utility/LockPool/PidLock.hs
@@ -32,17 +32,17 @@ import Prelude
-- Takes a pid lock, blocking until the lock is available or the timeout.
waitLock :: Seconds -> LockFile -> IO LockHandle
-waitLock timeout file = makeLockHandle
+waitLock timeout file = makeLockHandle P.lockPool file
-- LockShared for STM lock, because a pid lock can be the top-level
-- lock with various other STM level locks gated behind it.
- (P.waitTakeLock P.lockPool file LockShared)
- (mk <$> F.waitLock timeout file)
+ (\p f -> P.waitTakeLock p f LockShared)
+ (\f -> mk <$> F.waitLock timeout f)
-- Tries to take a pid lock, but does not block.
tryLock :: LockFile -> IO (Maybe LockHandle)
-tryLock file = tryMakeLockHandle
- (P.tryTakeLock P.lockPool file LockShared)
- (fmap mk <$> F.tryLock file)
+tryLock file = tryMakeLockHandle P.lockPool file
+ (\p f -> P.tryTakeLock p f LockShared)
+ (\f -> fmap mk <$> F.tryLock f)
checkLocked :: LockFile -> IO (Maybe Bool)
checkLocked file = P.getLockStatus P.lockPool file