mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-09-20 21:16:22 +02:00
763d72238d
It is possible that a scheduled channel ended up with 0 bytes in its outbuf after the scheduling loop and having an outbuf table entry indicating that we need to flush bytes on the wire after the loop. This lead to attempt to write 0 bytes up to the TLS layer that would prevent such action. All in all, this fixes wasted CPU cycles on attempting to flush nothing. Fixes #40548 Signed-off-by: David Goulet <dgoulet@torproject.org>
5 lines
241 B
Plaintext
5 lines
241 B
Plaintext
o Minor bugfixes (cell scheduling):
|
|
- Don't attempt to write 0 bytes after a cell scheduling loop. No empty
|
|
payload was put on the wire. Fixes bug 40548; bugfix on 0.3.5.1-alpha.
|
|
- Avoid writing empty payload with NSS write.
|