[tor-bugs] #33131 [Core Tor/Tor]: Bug: buf->datalen >= 0x7fffffff

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#33131: Bug: buf->datalen >= 0x7fffffff
--------------------------+------------------------------
 Reporter:  cypherpunks   |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Component:  Core Tor/Tor
  Version:  Tor: 0.4.2.5  |       Severity:  Minor
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------
 With

 {{{
 BandwidthRate
 }}}

 set greater than 2147483646 bytes, for example Config line:

 {{{
 BandwidthRate 2147483647
 #same as
 BandwidthRate 2 GBytes
 }}}

  no streams complete in my relay and this Bug message appears:


 {{{
 Feb 02 06:32:37.000 [warn] {BUG} tor_bug_occurred_(): Bug:
 buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(ASSERT_PREDICT
 _UNLIKELY_(buf->datalen >= 0x7fffffff - at_most)) failed. (Future
 instances of this warning will be silenced.) (on Tor 0.4.2.5 )
 Feb 02 06:32:37.000 [warn] {BUG} Bug: Tor 0.4.2.5: Non-fatal assertion
 !(ASSERT_PREDICT_UNLIKELY_(buf->datalen >= 0x7fffffff - at_mo
 st)) failed in buf_read_from_tls at buffers_tls.c:73. (Stack trace not
 available) (on Tor 0.4.2.5 )
 }}}


 Looks like some INT_MAX buffer count trouble to me at least.



 {{{

 # BandwidthRate BandwidthRate __N__
 bytes|KBytes|MBytes|GBytes|TBytes|KBits|MBits|GBits|TBits
 #     A token bucket limits the average incoming bandwidth usage on this
 node
 #     to the specified number of bytes per second, and the average
 outgoing
 #     bandwidth usage to that same value.  If you want to run a relay in
 the
 #     public network, this needs to be _at the very least_ 75 KBytes for a
 #     relay (that is, 600 kbits) or 50 KBytes for a bridge (400 kbits) --
 but of
 #     course, more is better; we recommend at least 250 KBytes (2 mbits)
 if
 #     possible.  (Default: 1 GByte) +
 #  +
 #     Note that this option, and other bandwidth-limiting options, apply
 to TCP
 #     data only: They do not count TCP headers or DNS traffic. +
 #  +
 #     With this option, and in other options that take arguments in bytes,
 #     KBytes, and so on, other formats are also supported. Notably,
 "KBytes" can
 #     also be written as "kilobytes" or "kb"; "MBytes" can be written as
 #     "megabytes" or "MB"; "kbits" can be written as "kilobits"; and so
 forth.
 #     Tor also accepts "byte" and "bit" in the singular.
 #     The prefixes "tera" and "T" are also recognized.
 #     If no units are given, we default to bytes.
 #     To avoid confusion, we recommend writing "bytes" or "bits"
 explicitly,
 #     since it's easy to forget that "B" means bytes, not bits.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33131>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs