Re: [PATCH] read/write: documentation of limits v3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jakub,

On Mon, 6 May 2019 at 08:31, Jakub Wilk <jwilk@xxxxxxxxx> wrote:
>
> * Shawn Landden <shawn@xxxxxxx>, 2019-05-06, 08:06:
> >--- a/man2/write.2
> >+++ b/man2/write.2
> >@@ -190,10 +190,18 @@ flag, and either the address specified in
> > .IR buf ,
> > the value specified in
> > .IR count ,
> > or the file offset is not suitably aligned.
> > .TP
> >+.B EINVAL
> >+.\" MAX_RW_COUNT in include/linux/fs.h
> >+The write amount is greater than
> >+.B MAX_RW_COUNT,
> >+which is
> >+.B INT_MAX
> >+rounded down to the page size (INT_MAX & ~PAGE_MASK).
> >+.TP
>
> I can't reproduce this. For me, write() behaves as it is documented in
> another part of this man page:
>
> "On Linux, write() (and similar system calls) will transfer at most
> 0x7ffff000 (2,147,479,552) bytes, returning the number of bytes actually
> transferred. (This is true on both 32-bit and 64-bit systems.)"
>
> I've attached the program that I used for testing.

Yes, I concur, and thanks for your independent testing. This is
longstanding Linux behaviour (see my other reply on the list a few
minutes ago).

Thanks,

MIchael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux