Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #8298

Closed (moved)
Open
Opened Feb 21, 2013 by cypherpunks@cypherpunks

Do not start write to connection if blocked on bw

Tor can to start write to connection just because something wrote to conn's outbuf by _connection_write_to_buf_impl(). While connection can be blocked on bw still. If buckets empty it can't to write anything anyway (need investigation for sure).

Suggested idea to fix, could be looks like:

  if (conn->write_event && !conn->write_blocked_on_bw) {
    connection_start_writing(conn);
  }

Kludgy probably. #8111 (moved) will fix it generally for 0.2.5 I hopes.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#8298