linux-kernel - Re: epoll design problems with common fork/exec patterns

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]

Message-ID: <Pine.LNX.4.64.0802281133020.7660@alien.or.mcafeemobile.com>
Date:	Thu, 28 Feb 2008 11:34:08 -0800 (PST)
From:	Davide Libenzi <davidel@...ilserver.org>
To:	Michael Kerrisk <mtk.manpages@...glemail.com>
cc:	Chris "弁" Heath <chris@...thens.co.nz>,
	David Schwartz <davids@...master.com>, dada1@...mosbay.com,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	linux-man@...r.kernel.org
Subject: Re: epoll design problems with common fork/exec patterns

On Thu, 28 Feb 2008, Michael Kerrisk wrote:

> Davide,
> 
> with the earlier discussion in this thread in mind, I added a Q0/A0 to
> epoll.7, just make the point about keys clear:
> 
> 
>        Q0  What is the key used to distinguish the file descrip-
>            tors in an epoll set?
> 
>        A0  The key is the combination  of  the  file  descriptor
>            number  and  the open file description (also known as
>            "open file handle", the kernel's internal representa-
>            tion of an open file).
> 
> Does that seem okay?

Looks fine to me! We need to clarify better Q6 WRT fork().



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