author | Jonathan Nieder <jrnieder@gmail.com> | |
Wed, 11 Jan 2012 23:50:10 +0000 (17:50 -0600) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 12 Jan 2012 01:37:10 +0000 (17:37 -0800) | ||
commit | 06121a0a8328c8aaa7a023cf6ebb142e9dc2b45c | |
tree | b0900ae8c603123769707ea636cced6ea5998c7f | tree | snapshot |
parent | 8ec6c8d79567a71ca3c6f1ec73eb453d371b1ade | commit | diff |
unix-socket: do not let close() or chdir() clobber errno during cleanup
unix_stream_connect and unix_stream_listen return -1 on error, with
errno set by the failing underlying call to allow the caller to write
a useful diagnosis.
Unfortunately the error path involves a few system calls itself, such
as close(), that can themselves touch errno.
This is not as worrisome as it might sound. If close() fails, this
just means substituting one meaningful error message for another,
which is perfectly fine. However, when the call _succeeds_, it is
allowed to (and sometimes might) clobber errno along the way with some
undefined value, so it is good higiene to save errno and restore it
immediately before returning to the caller. Do so.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
unix_stream_connect and unix_stream_listen return -1 on error, with
errno set by the failing underlying call to allow the caller to write
a useful diagnosis.
Unfortunately the error path involves a few system calls itself, such
as close(), that can themselves touch errno.
This is not as worrisome as it might sound. If close() fails, this
just means substituting one meaningful error message for another,
which is perfectly fine. However, when the call _succeeds_, it is
allowed to (and sometimes might) clobber errno along the way with some
undefined value, so it is good higiene to save errno and restore it
immediately before returning to the caller. Do so.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
unix-socket.c | diff | blob | history |