From: Ian Abbott <abbotti@mev.co.uk>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Ian Abbott <ian.abbott@mev.co.uk>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
H Hartley Sweeten <hartleys@visionengravers.com>
Subject: Re: [PATCH] staging: comedi: remove __user annotation inside of struct's
Date: Thu, 10 May 2012 12:05:26 +0100 [thread overview]
Message-ID: <4FABA0F6.6090401@mev.co.uk> (raw)
In-Reply-To: <20120509141920.GT22134@mwanda>
On 2012-05-09 15:19, Dan Carpenter wrote:
> On Wed, May 09, 2012 at 12:01:25PM +0100, Ian Abbott wrote:
>> Are there any handy macros for casting pointers to __user pointers,
>> something like
>>
>> #define _user(p) ((typeof(*(p)) __user *)(p))
>>
>> but preferably without the repeated expansion of 'p' in case of
>> side-effects?
>
> typeof() doesn't have side effects.
>
> #include<stdio.h>
>
> int main(void)
> {
> int x = 0;
> typeof(x++) y;
>
> printf("%d\n", x);
>
> return 0;
> }
>
> regards,
> dan carpenter
Yes, you're correct of course. I was unnecessarily worried about the
double-expansion of the macro parameter but it's safe in this case.
BTW, the intention of this macro is so you can write things like:
copy_from_user(data, _user(insn.data), insn.n * sizeof(insn.data[0]));
instead of:
copy_from_user(data, (unsigned int __user *)insn.data, insn.n *
sizeof(insn.data[0]));
where the member insn.data is a 'unsigned int *' but is used for both
__user pointers and kernel pointers.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2012-05-10 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 23:41 [PATCH] staging: comedi: remove __user annotation inside of struct's H Hartley Sweeten
2012-05-08 23:55 ` H Hartley Sweeten
2012-05-09 10:20 ` Ian Abbott
2012-05-09 10:31 ` Dan Carpenter
2012-05-09 11:01 ` Ian Abbott
2012-05-09 14:19 ` Dan Carpenter
2012-05-10 11:05 ` Ian Abbott [this message]
2012-05-09 14:24 ` gregkh
2012-05-09 15:52 ` H Hartley Sweeten
2012-05-09 15:56 ` gregkh
2012-05-09 16:03 ` H Hartley Sweeten
2012-05-09 16:41 ` H Hartley Sweeten
2012-05-09 20:42 ` gregkh
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=4FABA0F6.6090401@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hartleys@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.