[tor-bugs] #27241 [Core Tor/Tor]: Extract information from more kinds of wedged directory connections.

[Tor Bug Tracker & Wiki]

#27241: Extract information from more kinds of wedged directory connections.
--------------------------+------------------------------------
 Reporter:  nickm         |          Owner:  nickm
     Type:  enhancement   |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  fast-fix      |  Actual Points:
Parent ID:                |         Points:
 Reviewer:  mikeperry     |        Sponsor:  Sponsor8-can
--------------------------+------------------------------------

Comment (by mikeperry):

 To help me understand the consequences of this (and to figure out if I
 need to also do anything here for #25573), I have the following questions:

 1. How do stalled dirconns translate to their linked edge_connection_ts?
 Can the edge connection "stall" first and/or get closed somewhere else, or
 will the dirconn always be the thing that stalls?
 2. What are the consequences to the dir conn if some other code marks the
 edge connnection is closed first?
 3. When the dirconn is closed first (such as here or elsewhere in the
 code), where in the code do we decide to mark/clean up/close the
 corresponding linked edge conn? I could not find this..

 For #25573, I'm particularly concerned about multihop hsdir dirconns. But
 if we ever make regular directory activity multihop, this could apply
 there too. Plus the linked conn close conditions may be relevant to this
 bug?

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