diff options
| author | Nick Mathewson <nickm@torproject.org> | 2007-10-11 20:45:26 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2007-10-11 20:45:26 +0000 |
| commit | b62d379f9274c219615520d6805a4fa985970faf (patch) | |
| tree | 6664addacf93cd83f0d9c6414ac13719f8273ba6 /ChangeLog | |
| parent | 375acaab2666a7fcfcb79e5d6c9b6d0ad52a3e8c (diff) | |
| download | tor-b62d379f9274c219615520d6805a4fa985970faf.tar tor-b62d379f9274c219615520d6805a4fa985970faf.tar.gz | |
r15689@catbus: nickm | 2007-10-11 16:40:25 -0400
Fix bug 451. This was a nasty bug, so let's fix it twice: first, by banning recursive calls to connection_handle_write from connection_flushed_some; and second, by not calling connection_finished_flushing() on a closed connection. Backport candidate.
svn:r11882
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -35,6 +35,18 @@ Changes in version 0.2.0.8-alpha - 2007-10-12 string which usually wasn't there, once for every routerinfo we read, just scan lines forward until we find one we like. Bugfix on 0.2.0.1. + - When we add data to a write buffer in response to the data on that + write buffer getting low because of a flush, do not consider the newly + added data as a candidate for immediate flushing, but rather make it + wait until the next round of writing. Otherwise, we flush and refill + recursively, and a single greedy TLS connection can eat all of our + bandwidth. Bugfix on 0.1.2.7-alpha. + + o Major bugfixes (crashes): + - If a connection is shut down abruptly because of something that + happened inside connection_flushed_some(), do not call + connection_finished_flushing(). Should fix bug 451. Bugfix on + 0.1.2.7-alpha. o Minor features (v3 authority system): - Add more ways for tools to download the votes that lead to the |