[Bug 276937] read(2) is documented as returning EINVAL on reads above INT_MAX

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276937

            Bug ID: 276937
           Summary: read(2) is documented as returning EINVAL on reads
                    above INT_MAX
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Manual Pages
          Assignee: bugs@FreeBSD.org
          Reporter: bugs.freebsd.org@masklinn.net
                CC: doc@FreeBSD.org

The man page for read(2) says:

> [EINVAL] The value nbytes is greater than INT_MAX.

the man page for write(2) says:

> [EINVAL] The value nbytes is greater than SSIZE_MAX (or greater than INT_MAX, if the sysctl debug.iosize_max_clamp is non-zero).

Experimentally, it looks like the behaviour of read(2) is identical to that of
write(2) (though I have not cared to try setting the sysctl).

I assume when IO limitations were relaxed and the sysctl was added, man read(2)
was missed and never updated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.