Messages in this thread | | | Date | Thu, 09 Oct 2008 13:52:50 -0700 | From | Ulrich Drepper <> | Subject | Re: dup2() vs dup3() inconsistency when |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
H. Peter Anvin wrote: > The result of dup3(fd, fd, O_CLOEXEC) is to set the O_CLOEXEC flag on fd.
That's bad and disregarded by Al and myself because it is one and the same descriptor and therefore it changes the source descriptor.
> Step (2) could be considered a bit dubious, but the behaviour of > dup2(fd, fd) is a direct consequence of the chosen semantics.
The behavior of dup2(fd,fd) is just a result of an accident in the original implementation. It makes no sense and the mistake doesn't have to be repeated.
- -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkjubyIACgkQ2ijCOnn/RHRIMwCfdFeW08lSPRh12C+qKzF99AWf idEAn0x0jqcVEIzmcgIVuZLlHKleNmC0 =Dx/d -----END PGP SIGNATURE----- -- 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/
| |