Date: 17 Jul 2001 21:43:17 +0200 From: Dag-Erling Smorgrav <des@ofug.org> 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: <xzpr8vf1gve.fsf@flood.ping.uio.no> In-Reply-To: <20010716181456.A56285@ringworld.oblivion.bg> References: <200107161435.f6GEZM631927@coffee.q9media.com> <20010716181456.A56285@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Pentchev <roam@orbitel.bg> writes:
> 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.
You can work around this by casting the LHS to (const char *):
(const char *)iov[n].iov_base = str;
iov[n].iov_len = len;
DES
--
Dag-Erling Smorgrav - des@ofug.org
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?xzpr8vf1gve.fsf>