mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 13:13:44 +01:00
95238eb917
When we close a connection via connection_close_immediately, we kill
its events immediately. But if it had been blocked on bandwidth
read/write, we could try to re-add its (nonexistent) events later
from connection_bucket_refill -- if we got to that callback before
we swept the marked connections.
Fixes bug 24167. Fortunately, this hasn't been a crash bug since we
introduced connection_check_event in 0.2.9.10, and backported it.
This is a bugfix on commit 89d422914a, I believe, which
appeared in Tor 0.1.0.1-rc.
8 lines
378 B
Plaintext
8 lines
378 B
Plaintext
o Minor bugfixes (network layer):
|
|
- When closing a connection via close_connection_immediately(), we
|
|
mark it as "not blocked on bandwidth", to prevent later calls
|
|
from trying to unblock it, and give it permission to read. This
|
|
fixes a backtrace warning that can happen on relays under various
|
|
circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
|
|
|