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
Date: Mon, 14 Jun 2004 19:30:18 +0100 [thread overview]
Message-ID: <20040614183017.GB12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1087235597.10368.12.camel@stevef95.austin.ibm.com>
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).
prev parent reply other threads:[~2004-06-14 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 17:53 Steve French
2004-06-14 18:30 ` viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040614183017.GB12308@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=smfltc@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®