In message <202010260059.09q0xbxt003...@slippy.cwsent.com>, Cy Schubert writes: > In message <202010260037.09q0bvpn090...@repo.freebsd.org>, John-Mark Gurney > wri > tes: > > Author: jmg > > Date: Mon Oct 26 00:37:31 2020 > > New Revision: 367048 > > URL: https://svnweb.freebsd.org/changeset/base/367048 > > > > Log: > > update write(2)'s iovec limit w/ info about the iosize_max_clamp sysctl.. > . > > > > Modified: > > head/lib/libc/sys/write.2 > > > > Modified: head/lib/libc/sys/write.2 > > =========================================================================== > == > > = > > --- head/lib/libc/sys/write.2 Sun Oct 25 23:26:07 2020 (r36704 > 7) > > +++ head/lib/libc/sys/write.2 Mon Oct 26 00:37:31 2020 (r36704 > 8) > > @@ -28,7 +28,7 @@ > > .\" @(#)write.2 8.5 (Berkeley) 4/2/94 > > .\" $FreeBSD$ > > .\" > > -.Dd March 30, 2020 > > +.Dd October 25, 2020 > > .Dt WRITE 2 > > .Os > > .Sh NAME > > @@ -240,9 +240,13 @@ array was negative. > > .It Bq Er EINVAL > > The sum of the > > .Fa iov_len > > -values in the > > -.Fa iov > > -array overflowed a 32-bit integer. > > +values is greater than > > +.Dv SSIZE_MAX > > +(or greater than > > +.Dv INT_MAX , > > +if the sysctl > > +.Va debug.iosize_max_clamp > > Should we also include SEE ALSO reference to sysctl(8) or sysctl(3)? > Personally I think a reference to sysctl(8) would be more apropos.
Or maybe both. -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org NTP: <c...@nwtime.org> Web: https://nwtime.org The need of the many outweighs the greed of the few. _______________________________________________ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
