From owner-freebsd-audit Mon Jul 16 9:51:49 2001 Delivered-To: freebsd-audit@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 64EAB37B403 for ; Mon, 16 Jul 2001 09:51:45 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA19419; Tue, 17 Jul 2001 02:51:17 +1000 Date: Tue, 17 Jul 2001 02:49:02 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Pentchev Cc: Mike Barcroft , David Malone , audit@FreeBSD.ORG Subject: Re: inetd(8) warns patch In-Reply-To: <20010716181456.A56285@ringworld.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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