linux-kernel - Re: PROBLEM: Epoll frequently fails to notify connects at connect bursts

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: <20090826122641.GA29299@sirena.org.uk>
Date:	Wed, 26 Aug 2009 13:26:43 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Will Brown <dr.hfuhruhurr@...il.com>
Cc:	Davide Libenzi <davidel@...ilserver.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: Epoll frequently fails to notify connects at connect
	bursts

On Wed, Aug 26, 2009 at 11:15:10AM +0200, Will Brown wrote:
> On Wed, Aug 26, 2009 at 3:24 AM, Davide Libenzi<davidel@...ilserver.org> wrote:

> >> Multiple quasi-simultaneous events for the same fd are merged. This is why
> >> on POLLIN on accepting sockets you want to do something like:

> Aha! Thank you immensely Davide. It cost me one week of frustration already.

> 1. Where should I have picked up this gem of essential information? I
> haven't seen it in the man-pages for either 'epoll' or 'accept'.

It should be covered in the "Level-Triggered and Edge-Triggered" section
of the epoll() manual page - the particular case of accept() isn't
covered but the general idea is the same.
--
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/