summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-25 17:57:15 -0400
committerNick Mathewson <nickm@torproject.org>2011-03-25 18:32:28 -0400
commit432734279d3688fafb466a23f43585ff509ff693 (patch)
treef76a2d010a699abaf0767d144f50d9fd41f3095a /changes
parentf3b89c114112987b74bb0632cfe47a3a17859adb (diff)
downloadtor-432734279d3688fafb466a23f43585ff509ff693.tar.gz
tor-432734279d3688fafb466a23f43585ff509ff693.zip
Fix handling of StreamID exhaustion.
Since svn r1475/git 5b6099e8 in tor-0.0.6, we have responded to an exhaustion of all 65535 stream IDs on a circuit by marking that circuit for close. That's not the right response. Instead, we should mark the circuit as "too dirty for new circuits". Of course in reality this isn't really right either. If somebody has managed to cram 65535 streams onto a circuit, the circuit is probably not going to work well for any of those streams, so maybe we should be limiting the number of streams on an origin circuit concurrently. Also, closing the stream in this case is probably the wrong thing to do as well, but fixing that can also wait.
Diffstat (limited to 'changes')
-rw-r--r--changes/full_ap_circuits6
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/full_ap_circuits b/changes/full_ap_circuits
new file mode 100644
index 0000000000..379a1a1b73
--- /dev/null
+++ b/changes/full_ap_circuits
@@ -0,0 +1,6 @@
+ o Minor bugfixes
+ - When a client finds that an origin circuit has run out of 16-bit
+ stream IDs, we now mark it as unusable for new streams.
+ Previously, we would try to close the entire circuit. Bugfix on
+ Tor version 0.0.6.
+