linux-kernel - Re: No NONBLOCK flag for dup3() or epoll

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 24 Aug 2008 12:35:33 -0700 (PDT)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Michael Kerrisk <mtk.manpages@...glemail.com>
cc:	Ulrich Drepper <drepper@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: No NONBLOCK flag for dup3() or epoll_create1()?

On Wed, 20 Aug 2008, Michael Kerrisk wrote:

> 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.

Traditionally the no-wait epoll_wait() has been achieved with a zero 
timeout, but _NONBLOCK support can be easily added if seen as necessary.



- Davide


--
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/