From: Christoph Hellwig <hch@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] linux/uio.h: cleanup for userspace
Date: Mon, 29 Dec 2008 08:03:53 -0500 [thread overview]
Message-ID: <20081229130353.GA10167@infradead.org> (raw)
In-Reply-To: <1230555599-23568-1-git-send-email-vapier@gentoo.org>
On Mon, Dec 29, 2008 at 07:59:59AM -0500, Mike Frysinger wrote:
> Hide iov_shorten() behind __KERNEL__ since it's a prototype only. Use the
> __inline__ form for iov_length() since it's usable by userspace.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> v3
> - keep all __KERNEL__ stuff in one place
> v2
> - drop inline conversion stuff
>
> include/linux/uio.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/uio.h b/include/linux/uio.h
> index b7fe138..3debd89 100644
> --- a/include/linux/uio.h
> +++ b/include/linux/uio.h
> @@ -26,6 +26,8 @@ struct kvec {
> size_t iov_len;
> };
>
> +unsigned long iov_shorten(struct iovec *iov, unsigned long nr_segs, size_t to);
> +
> #endif
>
> /*
> @@ -52,6 +54,4 @@ static inline size_t iov_length(const struct iovec *iov, unsigned long nr_segs)
> return ret;
> }
>
> -unsigned long iov_shorten(struct iovec *iov, unsigned long nr_segs, size_t to);
> -
> #endif
Umm, iov_length is another kernel-only thing and should not be left
user-visible. And struct kvec is in another __KERNEL__ block.
Just move UIO_FASTIOV and UIO_MAXIOV up and have a single __KERNEL__
block for the rest.
next prev parent reply other threads:[~2008-12-29 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 6:49 [PATCH] " Mike Frysinger
2008-12-29 12:20 ` [PATCH v2] " Mike Frysinger
2008-12-29 12:56 ` Sam Ravnborg
2008-12-29 12:59 ` [PATCH v3] " Mike Frysinger
2008-12-29 13:03 ` Christoph Hellwig [this message]
2008-12-29 20:32 ` [PATCH v4] " Mike Frysinger
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=20081229130353.GA10167@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.org \
/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®