Re: No Bug: accept discards socket options/O_NONBLOCK

From: Matthias Andree (matthias.andree@stud.uni-dortmund.de)
Date: Fri Sep 15 2000 - 22:58:06 EST


On Fri, 15 Sep 2000, D. J. Bernstein wrote:

> O_NONBLOCK is not an fd property. It is an ofile property. Two different
> fds created by dup() will point to the same O_NONBLOCK bit.

Who says that accept() is to use dup()?

There is a difference in "new file descriptor" (what accept returns) and
"copy of the file descriptor" (what dup returns).

You are relying on unspecified implementation details(*) and claiming Linux
was buggy. Please show papers that document either that accept must use
dup or that accept must copy file descriptor flags before claiming
someone else misbehaving.

*) unspecified as per SUS v2, Linux, FreeBSD, OpenBSD, NetBSD, Solaris,
HP-UX manual pages.

-- 
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:12 EST