Messages in this thread | | | Subject | Re: close return value | From | Florian Weimer <> | Date | Sat, 20 Jul 2002 10:00:00 +0200 |
| |
Linus Torvalds <torvalds@transmeta.com> writes:
> Yes, EAGAIN doesn't really work as a close return value, simply because > _nobody_ expects that (and leaving the file descriptor open after a > close() is definitely unexpected, ie people can very validly complain > about buggy behaviour).
Returning an error and still doing the operation is slightly awkward. Are there any other syscalls which do similar things?
Of course, a significant portion of TCP related code would leak descriptors like hell if the behavior of close() ischanged (there are quite a few protocols which do not avoid race conditions resulting in ECONNRESET connection teardown).
-- Florian Weimer Weimer@CERT.Uni-Stuttgart.DE University of Stuttgart http://CERT.Uni-Stuttgart.DE/people/fw/ RUS-CERT fax +49-711-685-5898 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |