BIND 10 #2198: make sure InterprocessSyncLocker is thread safe
BIND 10 Development
do-not-reply at isc.org
Tue Oct 16 01:03:38 UTC 2012
#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
Reporter: | Owner: muks
jinmei | Status: closed
Type: | Milestone:
defect | Sprint-20121023
Priority: | Resolution: fixed
medium | Sensitive: 0
Component: | Sub-Project: Core
logging | Estimated Difficulty: 5
Keywords: | Total Hours: 3.25
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by muks):
* status: reviewing => closed
* resolution: => fixed
Comment:
Merged to `master` in commit `f8181bb72251fd3d5f33e157d1f2a2a75a58d765`:
{{{
* 6adfc24 [2198] Don't return anything from thread functions
* 5b78174 [2198] Update comment
* 4ed683c [2198] Test the non-blocking variant of Mutex::Locker
* e6ac5ef [2198] Check pthread_mutex_trylock()'s return value
* 48e80a5 [2198] Revert include to local
* fff8929 [2198] Stop using direct lock methods on Mutex inside
InterprocessSyncFile
* ecef170 [2198] Make direct methods on Mutex private
* 350c775 [2198] Add a block argument to Mutex::Locker constructor
* 666bfa9 [2198] Add AlreadyLocked exception to Mutex::Locker
* d042cd0 [2198] Remove dependency on libb10-util in
src/lib/util/unittests/
* c0d25c4 [2198] First use a mutex for mutual exclusion among threads,
then a lock file
* e71cd13 [2198] Add Mutex::tryLock() and make lock methods public
* 6642455 [2198] Test that locks work from threads
* e562ac7 [2198] Build threads directory first because . depends on it
}}}
Resolving as fixed. Thank you for the reviews.
--
Ticket URL: <http://bind10.isc.org/ticket/2198#comment:22>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list