e52653e01a
USe uintptr_t for unsigned ints
2019-03-12 12:14:22 +02:00
052ec08a08
Refrain from doing exhaustive iteration over all values of integers
2019-03-12 12:01:26 +02:00
d731ab4583
Check that all valid values of int and unsigned int can be put into void pointer
2019-02-25 20:04:02 +02:00
69238ca2da
Merge remote-tracking branch 'tor-github/pr/646'
2019-02-24 17:17:16 -05:00
34601105a3
Merge branch 'ticket29065_squashed'
2019-02-24 17:02:35 -05:00
b7dced893a
Fix shellcheck SC2006 warnings in test_switch_id.sh
2019-02-24 17:02:06 -05:00
f229a33685
Merge remote-tracking branch 'nickm/thread_rng'
2019-02-22 16:07:57 +02:00
54e42fe364
Merge branch 'maint-0.4.0'
2019-02-21 10:08:14 -05:00
00a93b19cf
Merge branch 'maint-0.3.5' into maint-0.4.0
2019-02-21 10:08:14 -05:00
4a8a1f76ea
Merge branch 'maint-0.3.4' into maint-0.3.5
2019-02-21 10:08:14 -05:00
5062647918
Merge branch 'maint-0.3.3' into maint-0.3.4
2019-02-21 10:08:14 -05:00
be84ed1a64
kist: Don't write above the highwater outbuf mark
...
KIST works by computing how much should be allowed to write to the kernel for
a given socket, and then it writes that amount to the outbuf.
The problem is that it could be possible that the outbuf already has lots of
data in it from a previous scheduling round (because the kernel is full/busy
and Tor was not able to flush the outbuf yet). KIST ignores that the outbuf
has been filling (is above its "highwater") and writes more anyway. The end
result is that the outbuf length would exceed INT_MAX, hence causing an
assertion error and a corresponding "Bug()" message to get printed to the
logs.
This commit makes it for KIST to take into account the outbuf length when
computing the available space.
Bug found and patch by Rob Jansen.
Closes #29168 . TROVE-2019-001.
Signed-off-by: David Goulet <dgoulet@torproject.org >
2019-02-21 10:07:34 -05:00
df3484b2b0
Bump version to 0.4.0.2-alpha
2019-02-21 09:52:27 -05:00
c663716b67
Bump to 0.3.5.8
2019-02-21 09:51:29 -05:00
508002a4c2
Bump to 0.3.4.11
2019-02-21 09:50:22 -05:00
41c2bf590b
Update to 0.3.3.12
2019-02-21 09:49:48 -05:00
aa79196ee0
Merge branch 'maint-0.4.0'
2019-02-21 09:10:34 -05:00
34183f0d71
Fix a goofy change from abcde10fce that broke test-slow linking
...
boklm tracked this down, and it doesn't make sense. It caused
This change goes back to the previous LDFLAGS line.
2019-02-21 09:10:15 -05:00
da179088ee
Merge branch 'tor-github/pr/687'
2019-02-20 12:09:02 -05:00
7037fe1163
Merge branch 'tor-github/pr/700'
2019-02-20 12:06:39 -05:00
b7ad8bcaad
Use setrlimit instead of ulimit -c in backtrace tests
2019-02-20 12:06:26 -05:00
8f5a3c0460
Merge branch 'tor-github/pr/675'
2019-02-20 11:45:58 -05:00
a30f17f72f
Merge branch 'tor-github/pr/696'
2019-02-20 11:29:55 -05:00
c22446e305
Merge branch 'maint-0.4.0'
2019-02-20 10:40:20 -05:00
5ec65be8bf
Merge remote-tracking branch 'nickm/ticket29530_040' into maint-0.4.0
2019-02-20 10:39:28 -05:00
4d4eda89a1
Merge branch 'maint-0.4.0'
2019-02-20 10:36:54 -05:00
ccab4347e5
Merge remote-tracking branch 'nickm/ticket29534_040' into maint-0.4.0
2019-02-20 10:35:56 -05:00
249319ec5d
fix typos from #28614
2019-02-20 10:32:47 -05:00
208f04e9b8
Add a quick test for get_thread_fast_rng()
2019-02-19 15:36:11 -05:00
b25cd5cfe1
Implement code to manage a per-thread instance of crypto_fast_rng()
...
The subsystems API makes this really simple, fortunately.
Closes ticket 29536
2019-02-19 15:36:08 -05:00
d32e407976
Downgrade some LOG_ERR messages in the address/* tests to warnings
...
Fixes bug 29530, where the LOG_ERR messages were occurring when
we had no configured network, and so we were failing the unit tests
because of the recently-merged #28668 .
Bug not in any released Tor.
2019-02-19 14:02:32 -05:00
c9ff6a7f83
Mark map_anon_nofork test as skipped in 0.4.0
...
This test fails in some environments; since the code isn't used in
0.4.0, let's disable it for now.
Band-aid solution for #29534 ; bug not in any released Tor.
2019-02-19 13:14:26 -05:00
6927e9a60c
Merge remote-tracking branch 'tor-github/pr/665'
2019-02-19 11:56:48 -05:00
c3fca4e4b3
Merge branch 'maint-0.4.0'
2019-02-19 11:51:24 -05:00
4df31adef7
Merge remote-tracking branch 'tor-github/pr/704' into maint-0.4.0
2019-02-19 11:51:19 -05:00
f70929347f
Merge branch 'maint-0.4.0'
2019-02-19 11:49:24 -05:00
4bc55ed5ee
Merge branch 'bug29145_029' into maint-0.4.0
2019-02-19 11:49:20 -05:00
4417ac880a
Fix a compiler warning on OpenBSD
...
malloc_options needs to be declared extern (and declaring it extern
means we need to initialize it separately)
Fixes bug 29145; bugfix on 0.2.9.3-alpha
Signed-off-by: Kris Katterjohn <katterjohn@gmail.com >
2019-02-19 11:38:32 -05:00
17e29bda5d
Merge branch 'maint-0.4.0'
2019-02-19 11:34:25 -05:00
b5f3a3d6a7
Merge remote-tracking branch 'tor-github/pr/707' into maint-0.4.0
2019-02-19 11:34:21 -05:00
1239e411a7
Merge remote-tracking branch 'tor-github/pr/694'
2019-02-19 11:31:22 -05:00
0db0b4769c
Merge remote-tracking branch 'tor-github/pr/678'
2019-02-19 11:30:27 -05:00
8a5c66cbb0
Merge branch 'maint-0.4.0'
2019-02-19 11:27:21 -05:00
26873bc4ed
Merge branch 'bug28698_035' into maint-0.4.0
2019-02-19 11:27:18 -05:00
78220aae1e
Add circuit time check before logging about relaxing circuit time
...
Signed-off-by: José M. Guisado <guigom@riseup.net >
2019-02-19 11:24:51 -05:00
485803dffe
Merge branch 'maint-0.4.0'
2019-02-19 11:21:54 -05:00
5c87add923
Merge remote-tracking branch 'tor-github/pr/701' into maint-0.4.0
2019-02-19 11:21:51 -05:00
9a158a45b1
Bump to 0.4.1.0-alpha-dev
2019-02-19 09:29:43 -05:00
94f7e53d04
fix a bootstrapping string typo
...
introduced in 85542ee5
2019-02-17 16:56:13 -05:00
384c5c6188
Make test-slow compile with libevent
2019-02-16 16:03:17 -05:00
rl1987
Nick Mathewson
George Kadianakis
David Goulet
Roger Dingledine
Kris Katterjohn
José M. Guisado
Neel Chauhan