aboutsummaryrefslogtreecommitdiffstats
path: root/src/hash
diff options
context:
space:
mode:
authorlloyd <[email protected]>2011-07-05 20:45:23 +0000
committerlloyd <[email protected]>2011-07-05 20:45:23 +0000
commit1dbbec7519d75f7bc5b8fa23eb175c8a8f96a9b5 (patch)
tree4b2096bb10cd4de87fcd8aef7549e39cc1a0c95d /src/hash
parentb16bd4ad156f954dbcd4299e298765eececac19d (diff)
The Algorithm_Factory has this logic on looking for an object:
- Check the cache; if found, return value - Populate cache, if the value is already there, delete the old object and save the new one. - Recheck the cache value Raja <[email protected]> pointed out on the list that this could race if multiple threads called a lookup function in close succession while the cache was cold. All of them would fail the lookup, then each of them would add it, but the values returned would be deleted by other threads. Instead, declare that first write wins. Then, the cache stays consistent even if there is a race, the only issue is an extra search and delete. Modify GOST and Skein, as their name() function did not roundtrip properly which caused failures otherwise.
Diffstat (limited to 'src/hash')
-rw-r--r--src/hash/skein/skein_512.cpp2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/hash/skein/skein_512.cpp b/src/hash/skein/skein_512.cpp
index f85968e84..571bf9c0b 100644
--- a/src/hash/skein/skein_512.cpp
+++ b/src/hash/skein/skein_512.cpp
@@ -184,6 +184,8 @@ Skein_512::Skein_512(size_t arg_output_bits,
std::string Skein_512::name() const
{
+ if(personalization != "")
+ return "Skein-512(" + to_string(output_bits) + "," + personalization + ")";
return "Skein-512(" + to_string(output_bits) + ")";
}