diff options
| author | David Goulet <dgoulet@torproject.org> | 2022-02-08 09:31:17 -0500 |
|---|---|---|
| committer | David Goulet <dgoulet@torproject.org> | 2022-02-08 09:31:17 -0500 |
| commit | 763d72238d84ff5c2c0a889d15f25a145046c9e5 (patch) | |
| tree | e03d4f7d4d111e90fec4eba519901a8390cd2b4e /changes | |
| parent | 9bf4a9e18a244dd9930a906e92d1f33bbc3bbf13 (diff) | |
| download | tor-763d72238d84ff5c2c0a889d15f25a145046c9e5.tar.gz tor-763d72238d84ff5c2c0a889d15f25a145046c9e5.zip | |
kist: Don't try to flush empty outbuf
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>
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/ticket40548 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/ticket40548 b/changes/ticket40548 new file mode 100644 index 0000000000..277bb577a4 --- /dev/null +++ b/changes/ticket40548 @@ -0,0 +1,4 @@ + 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. |