BIND 10 #2398: msgq crash

[BIND 10 Development]

#2398: msgq crash
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  jelte
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:         |  Sprint-20121204
  medium                             |            Resolution:
                  Component:  msgq   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  Core
            Defect Severity:  High   |  Estimated Difficulty:  4
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 There are still few things:
  * Would it be worth it unifying `send_prepared_msg` and
 `__process_write`? They seem they share a lot of common code now.
  * Is it OK? Couldn't it lead to some kind of starvation of one socket (if
 there was a really hight amount of data being sent, there'd always be
 something to write to the socket and it wouldn't get to the read).
 Arguably, there must be some reads somewhere to have writes, but there
 still can be one socket that is unlucky.
  * I don't like the way the running is set to false and then there's
 waiting until the read times out. Shouldn't the poll be waken up somehow?
 Waiting 2 seconds seems like a really long time.

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