Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Newsgroups: comp.os.linux.development.apps
Subject: Re: Linux O_NONBLOCK bug/ quirk
Date: Fri, 28 Mar 2014 12:45:22 +0000
Lines: 20
Message-ID: <87fvm28pb1.fsf@sable.mobileactivedefense.com>
References: <878urvu0gx.fsf@sable.mobileactivedefense.com> <lh3ako$mj6$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: individual.net 9A6SaKpe0kh1CLjNNnkUUgahdewOJv1eXZ12I4YGmJvFeHNSI=
Cancel-Lock: sha1:lt5G3YHNqDUNS4pGV1dL9gp4Cmk= sha1:qqf6hmQn8dqsycs27KIn+1DD7/M=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Xref: csiph.com comp.os.linux.development.apps:668

crankypuss <crankypuss@nomail.invalid> writes:
> On 03/27/2014 09:26 AM, Rainer Weikusat wrote:
>> As part of one of the usual 'pleasant exchanges' with the people whose
>> ability to make a living depends on controlling access to the Linux code
>> base, it came to light that a receive operation on a socket in
>> non-blocking mode can actually be blocked forever on Linux,

[example of a non-blocking read being 'frozen out' by a prior blocking one]

[...]

> So it goes.

Indeed. Software has bugs or 'unexpected features' in 'rarely used
corners' all the time. 

> The question of how these people allegedly control access
> to the linux codebase is fascinating.

Google "old boys network".