Bug#629994: sendfile returns early without user-visible reason
Please move this discussion somewhere else. I consider this no bug at all
and you failed to convince me.
On Fri, Jun 10, 2011 at 03:08:11PM +0200, Marc Lehmann wrote:
> On Fri, Jun 10, 2011 at 02:29:46PM +0200, Bastian Blank <waldi@debian.org> wrote:
> > > What the fuck, it's buggy, indeed:
> > > read(0, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 3298534883328) = 2147479552
> > What is the bug?
> Please *read* the bug report.
No. The bug report is about sendfile, not read.
> > > transfers as many bytes as can be transferred, and not stop a random
> > > amount earlier
> > Please quote the standard on this.
> Please *read* the bug report. You can also read the full read(2) sus
> manpage online at www.opengroup.org.
Please show the actual URI.
http://pubs.opengroup.org/onlinepubs/009695399/functions/read.html
sounds different for me.
> > Please note that A => B does not imply !A => !B (A == {not-regular,
> > signaled}, B == short-write).
> Reading standards is notoriously difficult, I admit. The behaviour of read
> is specified to read the requested number of bytes, if possible.
Please quote. You have not yet.
> The standard gives an exception list where applications can deviate from
> the behaviour and read less.
It defines some behaviours where it "shall" produce a different result.
They are not defined as exception of something.
> For other exceptions, you would have to find a part of the standard that
> actually allows it.
To find an exception, there needs to be a rule. Where is it?
Bastian
--
Even historians fail to learn from history -- they repeat the same mistakes.
-- John Gill, "Patterns of Force", stardate 2534.7
Reply to: