linux-kernel - RE: SELECT() returns 1 But FIONREAD says (Input/output error)

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: <MDEHLPKNGKAHNMBLJOLKCEBMEEAC.davids@webmaster.com>
Date:	Fri, 1 Jun 2007 10:33:44 -0700
From:	"David Schwartz" <davids@...master.com>
To:	<netbeans@...works.com>, <linux-kernel@...r.kernel.org>
Subject: RE: SELECT() returns 1 But FIONREAD says (Input/output error)

> The misunderstanding is from the docs.
> The select() does not report device errors.
> Select will just "more precisely, to see if a read will not block".

This is a much slighter misunderstanding. The result of the 'select'
function tells you nothing about what a particular 'read' will or will not
do. It's just a status reporting function. Saying that 'select' tells you 'a
read will not block' is as misleading as saying 'access' tells you if an
'open' will succeed.

All status reporting functions report status. You can phrase this about what
a hypothetical concurrent operation *would* *have* done. But it is
misleading to phrase it as what an actual future operation *will* do. The
kernel does not predict the future.

DS

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