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).

diff --git a/bluesky/log.c b/bluesky/log.c
index 19027da..b5c643f 100644 (file)
--- 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);