diff options
| author | Nick Mathewson <nickm@torproject.org> | 2011-03-25 16:14:42 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2011-03-25 18:32:28 -0400 |
| commit | 6a5b94de6c51478ca638ec03c40a6d3c27f2d674 (patch) | |
| tree | 14e4e6dc792d8137beac57bbfda94e2bb99b2295 /changes/connect_err_reporting | |
| parent | 05887f10ffe14498e96c34d2faa535187719689f (diff) | |
| download | tor-6a5b94de6c51478ca638ec03c40a6d3c27f2d674.tar tor-6a5b94de6c51478ca638ec03c40a6d3c27f2d674.tar.gz | |
Look at the right errno when sending reason for connect() failure
In afe414 (tor-0.1.0.1-rc~173), when we moved to
connection_edge_end_errno(), we used it in handling errors from
connection_connect(). That's not so good, since by the time
connection_connect() returns, the socket is no longer set, and we're
supposed to be looking at the socket_errno return value from
connection_connect() instead. So do what we should've done, and
look at the socket_errno value that we get from connection_connect().
Diffstat (limited to 'changes/connect_err_reporting')
| -rw-r--r-- | changes/connect_err_reporting | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/connect_err_reporting b/changes/connect_err_reporting new file mode 100644 index 000000000..61a46b658 --- /dev/null +++ b/changes/connect_err_reporting @@ -0,0 +1,6 @@ + o Minor bugfixes: + - Be more careful about reporting the correct error from a failed + connect() operation. Under some circumstances, it was possible to + look at an incorrect value for errno when sending the end reason. + Bugfix on Tor-0.1.0.1-rc. + |