summaryrefslogtreecommitdiff
path: root/unix-socket.c
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2017-02-17 16:07:49 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-02-17 14:40:29 -0800
commit7e8c9355b7aa61948275c8144dff6857f4b0ee51 (patch)
tree11fff8a46820416edfa1f2da44f448546e8c9e85 /unix-socket.c
parenttempfile: avoid "ferror | fclose" trick (diff)
downloadtgif-7e8c9355b7aa61948275c8144dff6857f4b0ee51.tar.xz
tempfile: set errno to a known value before calling ferror()
In close_tempfile(), we return an error if ferror() indicated a previous failure, or if fclose() failed. In the latter case, errno is set and it is useful for callers to report it. However, if _only_ ferror() triggers, then the value of errno is based on whatever syscall happened to last fail, which may not be related to our filehandle at all. A caller cannot tell the difference between the two cases, and may use "die_errno()" or similar to report a nonsense errno value. One solution would be to actually pass back separate return values for the two cases, so a caller can write a more appropriate message for each case. But that makes the interface clunky. Instead, let's just set errno to the generic EIO in this case. That's not as descriptive as we'd like, but at least it's predictable. So it's better than the status quo in all cases but one: when the last syscall really did involve a failure on our filehandle, we'll be wiping that out. But that's a fragile thing for us to rely on. In any case, we'll let the errno result from fclose() take precedence over our value, as we know that's recent and accurate (and many I/O errors will persist through the fclose anyway). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'unix-socket.c')
0 files changed, 0 insertions, 0 deletions