BIND 10 #952: msgq/cc multiple reads problem (and bad_alloc in b10-auth upon notify)

[BIND 10 Development]

#952: msgq/cc multiple reads problem (and bad_alloc in b10-auth upon notify)
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 in ticket #931, Michal discovered that there is a problem with multiple
 reads in cc/session. A (partial?) fix was proposed, and a different
 workaround was counterproposed (see that ticket).

 However, I also see problems that look like they are caused by the same or
 a very similar issue; upon notify, sometimes b10-auth aborts with a
 bad_alloc. The bad_alloc is caused by it trying to create a buffer for a
 message of which the length was incorrectly read.

 I think we should have locks around the different reads in session.cc

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