Zygo Blaxell c58e5cd75b crucible: cache: construct return value before releasing lock ...

If we release the lock first (and C++ destructor order says we do), then
the return value will be constructed from data living in an unprotected
container object.  That data might be destroyed before we get to the
copy constructor for the return value.

Make a temporary copy of the return value that won't be destroyed by any
other thread, then unlock the mutex, then return the copy object.

Signed-off-by: Zygo Blaxell <bees@furryterror.org>

2017-01-22 12:15:07 -05:00

..

crucible

crucible: cache: construct return value before releasing lock

2017-01-22 12:15:07 -05:00