BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

BIND 10 Development do-not-reply at isc.org
Tue Oct 23 00:29:19 UTC 2012


#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  muks
  jinmei                             |                Status:  reopened
                       Type:         |             Milestone:
  defect                             |  Sprint-20121023
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  Core
  logging                            |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  3.85
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by muks):

 The InterprocessSyncFile was written modifed assuming that a different
 instance would be used in each thread, i.e., different logger object in
 each thread, but re-reading the description, I think it wants the same
 logger object to be shared among threads. The lock was made to work among
 many threads, but it (the instance) itself cannot be shared.

 It can be fixed with more mutual exclusion. I'll revert the merge and fix
 it during the next sprint.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2198#comment:29>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list