aboutsummaryrefslogtreecommitdiffstats
path: root/src/libstrongswan/utils/utils.c
diff options
context:
space:
mode:
authorTobias Brunner <tobias@strongswan.org>2014-04-11 15:13:22 +0200
committerTobias Brunner <tobias@strongswan.org>2014-04-24 17:53:42 +0200
commitefedd0d21e4caf6edae6872f29c470a464e1917a (patch)
tree74b0784a419225a74f0ec73d148bfcd04c4a7345 /src/libstrongswan/utils/utils.c
parent1dfd11fd9249704ca29675c5ee11059a79aac203 (diff)
downloadstrongswan-efedd0d21e4caf6edae6872f29c470a464e1917a.tar.bz2
strongswan-efedd0d21e4caf6edae6872f29c470a464e1917a.tar.xz
utils: Add ref_cur() to retrieve the current value of a reference counter
On many architectures it is safe to read the value directly (those using cache coherency protocols, and with atomic loads for 32-bit values) but it is not if that's not the case or if we ever decide to make refcount_t 64-bit (load not atomic on x86). So make sure the operation is actually atomic and that users do not have to care about the size of refcount_t.
Diffstat (limited to 'src/libstrongswan/utils/utils.c')
-rw-r--r--src/libstrongswan/utils/utils.c14
1 files changed, 13 insertions, 1 deletions
diff --git a/src/libstrongswan/utils/utils.c b/src/libstrongswan/utils/utils.c
index fe80edb82..e4da6ddb9 100644
--- a/src/libstrongswan/utils/utils.c
+++ b/src/libstrongswan/utils/utils.c
@@ -528,7 +528,6 @@ refcount_t ref_get(refcount_t *ref)
pthread_mutex_lock(&ref_mutex);
current = ++(*ref);
pthread_mutex_unlock(&ref_mutex);
-
return current;
}
@@ -546,6 +545,19 @@ bool ref_put(refcount_t *ref)
}
/**
+ * Current refcount
+ */
+refcount_t ref_cur(refcount_t *ref)
+{
+ refcount_t current;
+
+ pthread_mutex_lock(&ref_mutex);
+ current = *ref;
+ pthread_mutex_unlock(&ref_mutex);
+ return current;
+}
+
+/**
* Single mutex for all compare and swap operations.
*/
static pthread_mutex_t cas_mutex = PTHREAD_MUTEX_INITIALIZER;