Stack Overflow has several examples where a function obtains an upgradeable lock first and then obtains exclusive access by upgrading. My understanding is that this can cause deadlocks if not used carefully since two threads may both obtain the upgradeable/shared lock and then both attempt to upgrade, at which point neither can proceed because the other has a shared lock.
What I want is to obtain the exclusive lock first and then downgrade to a shared lock without releasing the lock completely. I cannot find an example of this. Any ideas?
It seems the proper way to do this using lock adapters should be something like this:
There's an explicit conversion defined from
unique_lock
's RV refs toshared_lock
which calls theunlock_and_lock_shared( )
. See this e-mail thread and the source.Boost offers this functionality through the UpgradeLockable concept. The method you are looking for is
unlock_and_lock_shared()
.An implementation of this concept is provided by the
upgrade_mutex
class.