From 90e223dd5f5eeb9c87a6c5764b706a87695ec964 Mon Sep 17 00:00:00 2001
From: Michael Vrable <mvrable@cs.ucsd.edu>
Date: Mon, 20 Sep 2010 08:55:03 -0700
Subject: [PATCH] Remove an extraneous mutex unlock.

I'm surprised that this didn't cause trouble earlier; it seems that
unlocking an unlocked mutex raises no errors (but under heavy load, when
the mutex is locked by another thread then unlocking it can cause trouble).
---
 bluesky/log.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/bluesky/log.c b/bluesky/log.c
index 19027da..b5c643f 100644
--- a/bluesky/log.c
+++ b/bluesky/log.c
@@ -500,8 +500,6 @@ BlueSkyRCStr *bluesky_log_map_object(BlueSkyFS *fs, int log_dir,
         close(fd);
     }
 
-    g_mutex_unlock(log->mmap_lock);
-
     BlueSkyRCStr *str;
     map->atime = bluesky_get_current_time();
     str = bluesky_string_new_from_mmap(map, log_offset, log_size);
-- 
2.20.1