Date: Tue, 17 Jul 2001 02:49:02 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Peter Pentchev <roam@orbitel.bg> Cc: Mike Barcroft <mike@q9media.com>, David Malone <dwmalone@maths.tcd.ie>, audit@FreeBSD.ORG Subject: Re: inetd(8) warns patch Message-ID: <Pine.BSF.4.21.0107170245350.60058-100000@besplex.bde.org> In-Reply-To: <20010716181456.A56285@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Jul 2001, Peter Pentchev wrote: > On Mon, Jul 16, 2001 at 10:35:22AM -0400, Mike Barcroft wrote: > > Gererally speaking, it's usually a good idea to fix the root problem. > > If writev(2) and friends don't need to write to that variable, it's > > questionable why it's a char *. Some things just don't work with > > WARNS, such as RPC, because of library evilness. > > Basically, the problem is that although writev(2) doesn't need to write > to the buffer pointed to in its iov parameter, readv(2) does. > The obvious solution would be to separate the write- and read-vector > structures into two different iov_r and iov_w structures, but this > was not done back in 4.2BSD (when writev() and readv() appeared), > and trying to do it now would just create a gratuitous incompatibility > with next to all OS's out there.. And with POSIX.1-200x drafts. POSIX is only non-gratuitously incompatible (it changes the type of iov_base from "char *" to "void *"). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0107170245350.60058-100000>