Date: Mon, 14 Jun 2004 19:30:18 +0100
From: viro@parcelfarce.linux.theplanet.co.uk
To: Steve French <smfltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __user and iov_base
Message-ID: <20040614183017.GB12308@parcelfarce.linux.theplanet.co.uk>
References: <1087235597.10368.12.camel@stevef95.austin.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1087235597.10368.12.camel@stevef95.austin.ibm.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 793
Lines: 16

On Mon, Jun 14, 2004 at 12:53:18PM -0500, Steve French wrote:
> If a buffer is never used in user space, and is potentially recycled
> (via mempools) for use by more than one process, then it can't be passed
> around as an __user buffer, but is it ok to simply do
> 	myiovec.iov_base = (__user char *)some_buffer; 
> or is there another preferred way to handle kernel to __user
> mappings/casts?

Yes - leave them alone.  The warning points to real problem with the
interface; ergo, it should not disappear until there's a clean solution
(if ever).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/