]> git.ipfire.org Git - thirdparty/tor.git/commitdiff
buf_read_from_tls: Return ERROR_MISC, not WANTWRITE, on BUG().
authorNick Mathewson <nickm@torproject.org>
Wed, 29 Jan 2020 13:49:01 +0000 (08:49 -0500)
committerNick Mathewson <nickm@torproject.org>
Wed, 29 Jan 2020 13:50:03 +0000 (08:50 -0500)
Fixes bug 32673; bugfix on 0.3.0.4-alpha.  We introduced these
checks in ee5471f9aab5526 to help diagnose 21369, but we used "-1"
when "TOR_TLS_ERROR_MISC" would have been correct.  Found by opara.

I don't think that this is actually getting triggered in the wild,
but if it were, it could cause nasty behavior: spurious
WANTREAD/WANTWRITE returns have a way of turning into CPU-eating
busy-loops.

changes/bug32673 [new file with mode: 0644]
src/lib/tls/buffers_tls.c

diff --git a/changes/bug32673 b/changes/bug32673
new file mode 100644 (file)
index 0000000..32f02c6
--- /dev/null
@@ -0,0 +1,5 @@
+  o Minor bugfixes (TLS bug handling):
+    - When encountering a bug in buf_read_freom_tls(), return a
+      "MISC" error code rather than "WANTWRITE".  This change might
+      help avoid some CPU-wasting loops if the bug is ever triggered.
+      Bug reported by opara.    Fixes bug 32673; bugfix on 0.3.0.4-alpha.
index e92cb9163fa0f86ea5f3b54aa1c3f39725bdd717..52be78811d2792adbc9c44f579b25ba87c78bdd5 100644 (file)
@@ -69,9 +69,9 @@ buf_read_from_tls(buf_t *buf, tor_tls_t *tls, size_t at_most)
   check_no_tls_errors();
 
   IF_BUG_ONCE(buf->datalen >= INT_MAX)
-    return -1;
+    return TOR_TLS_ERROR_MISC;
   IF_BUG_ONCE(buf->datalen >= INT_MAX - at_most)
-    return -1;
+    return TOR_TLS_ERROR_MISC;
 
   while (at_most > total_read) {
     size_t readlen = at_most - total_read;