| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 20 Aug 2008 18:49:29 +0200 From: Michael Kerrisk <mtk.manpages@...glemail.com> To: Ulrich Drepper <drepper@...hat.com> CC: Andrew Morton <akpm@...ux-foundation.org>, Al Viro <viro@...iv.linux.org.uk>, lkml <linux-kernel@...r.kernel.org>, Davide Libenzi <davidel@...ilserver.org> Subject: No NONBLOCK flag for dup3() or epoll_create1()? Ulrich I've been doing some testing (2.6.27-rc3) of your new file-descriptor-creating syscalls that accept flags. According to http://udrepper.livejournal.com/20407.html all of the system calls should accept a *_NONBLOCK flag. All of them do, except for two: dup3(olfd, newfd, flags) and epoll_create1(flags). For epoll_create1() this certainly appears to be an oversight, since I can't think of a reason not to support *_NONBLOCK. For dup3() it is perhaps also an oversight. However, it's not really clear to me whether supporting O_NONBLOCK makes sense, since that would change the file status flags of the open file description that is (also) referred to by oldfd. (Furthermore, given a open file description for which O_NONBLOCK is already enabled, it is not possible to make a dup3() call that disables O_NONBLOCK, which is an odd asymmetry in the API.) What are your thoughts on this? Cheers, Michael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists