[tor-bugs] #5263 [Tor Relay]: Busy/infinite Libevent loops

[Tor Bug Tracker & Wiki]

#5263: Busy/infinite Libevent loops
------------------------+---------------------------------------------------
 Reporter:  robgjansen  |          Owner:                    
     Type:  defect      |         Status:  needs_review      
 Priority:  major       |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Relay   |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by nickm):

  * status:  new => needs_review


Comment:

 This is much simpler than the last version of this patch; thanks!

 >The reason that both read and write events are both de-registered when
 the marked connection can not flush is because both result in the same
 behavior. Both read/write events on marked connections will never again do
 any actual reads/writes, and are only useful to trigger the flush and
 close the connection.

 I think I agree with this patch except for this question.  Is it really
 the case that we reach this point with the connection still reading?  Keep
 in mind that this case can only happen if the connection is marked and is
 busy flushing; a connection in that condition *shouldn't* be reading.
 Did you run into some that were? If I missed something, though: sz==0 in
 that case doesn't mean that read is blocked on bandwidth; no read was
 attempted in the code above, and the read bucket wasn't examined.

 Can you tell me more about the read case here?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5263#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online