Nick Mathewson 62fb209d83 Stop frobbing timestamp_dirty as our sole means to mark circuits unusable ... In a number of places, we decrement timestamp_dirty by MaxCircuitDirtiness in order to mark a stream as "unusable for any new connections. This pattern sucks for a few reasons: * It is nonobvious. * It is error-prone: decrementing 0 can be a bad choice indeed. * It really wants to have a function. It can also introduce bugs if the system time jumps backwards, or if MaxCircuitDirtiness is increased. So in this patch, I add an unusable_for_new_conns flag to origin_circuit_t, make it get checked everywhere it should (I looked for things that tested timestamp_dirty), and add a new function to frob it. For now, the new function does still frob timestamp_dirty (after checking for underflow and whatnot), in case I missed any cases that should be checking unusable_for_new_conns. Fixes bug 6174. We first used this pattern in 516ef41ac1, which I think was in 0.0.2pre26 (but it could have been 0.0.2pre27).		2013-02-19 18:29:17 -05:00
..
common	Make _SC_OPEN_MAX actually get used when closing fds before exec.	2013-02-11 16:27:35 -05:00
config	Merge remote-tracking branch 'karsten/geoip-manual-update'	2013-02-08 10:37:34 -05:00
ext	Use torint.h in curve25519-donna*.c	2013-02-14 15:34:38 -05:00
or	Stop frobbing timestamp_dirty as our sole means to mark circuits unusable	2013-02-19 18:29:17 -05:00
test	Fix a may-be-used-uninitialized warning.	2013-02-19 15:00:08 -05:00
tools	Don't tor_close_socket(-1) in tor-resolve.	2013-02-11 17:32:58 -05:00
win32	Have autoconf check whether enums are signed.	2013-02-07 16:30:32 -05:00
include.am	Move all externally maintained source files into src/ext	2012-10-11 17:22:03 -04:00