BIND 10 #2038: zonemgr's config_handler doesn't provide strong exception guarantee

BIND 10 Development do-not-reply at isc.org
Wed Jun 13 21:09:10 UTC 2012


#2038: zonemgr's config_handler doesn't provide strong exception guarantee
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  high          |                    Milestone:  Next-
           Component:  secondary     |  Sprint-Proposed
  manager                            |                     Keywords:
           Sensitive:  0             |              Defect Severity:  N/A
         Sub-Project:  DNS           |  Feature Depending on Ticket:
Estimated Difficulty:  0             |          Add Hours to Ticket:  0
         Total Hours:  0             |                    Internal?:  0
-------------------------------------+-------------------------------------
 If I read it correct, zonemgr can partially update its internal
 configuration when it encounters an error in the middle of the update
 handler.  In particular, it can even partially update the
 "secondary_zones" list if there's an error in the middle of the list.

 This is generally bad, but now that ddns shares the config info it's
 even more serious: zonemgr and ddns could keep running with
 inconsistent information.  (And I misunderstood another related point:
 I thought cfgmr sent updates to "observer" modules that shows their
 interest in remote configs via add_remote_config, but on a closer look
 I realized cfgmgr doesn't actually distinguish the "real" module and
 "observers", and just broadcasts updates to all registered modules.
 IMO this behavior is also bad and should be fixed, but that's another
 topic).

-- 
Ticket URL: <http://bind10.isc.org/ticket/2038>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list