From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Real fix for rejected patch uaccess-warning
Date: Thu, 23 Mar 2006 15:58:45 -0500 [thread overview]
Message-ID: <20060323205845.GA6109@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200603101622.41518.blaisorblade@yahoo.it>
On Fri, Mar 10, 2006 at 04:22:41PM +0100, Blaisorblade wrote:
> 686: if (get_user(c, buf))
> where "buf" is a "const char __user *".
>
> It's complaining because "const" was lost.
>
> Ultimately, I think we should remove all this copying of pointers and do like
> i386 in this regard - there is only one cast to do, in put_user, as I
> mentioned in last mail.
OK, my first patch was insane, try this one:
Index: linux-2.6.15/include/asm-um/uaccess.h
===================================================================
--- linux-2.6.15.orig/include/asm-um/uaccess.h 2006-03-23 15:41:15.000000000 -0500
+++ linux-2.6.15/include/asm-um/uaccess.h 2006-03-23 15:48:52.000000000 -0500
@@ -42,10 +42,10 @@
#define __get_user(x, ptr) \
({ \
const __typeof__(ptr) __private_ptr = ptr; \
- __typeof__(*(__private_ptr)) __private_val; \
+ __typeof__(x) __private_val; \
int __private_ret = -EFAULT; \
(x) = (__typeof__(*(__private_ptr)))0; \
- if (__copy_from_user(&__private_val, (__private_ptr), \
+ if (__copy_from_user((void *) &__private_val, (__private_ptr), \
sizeof(*(__private_ptr))) == 0) {\
(x) = (__typeof__(*(__private_ptr))) __private_val; \
__private_ret = 0; \
The (void *) fixes the warnings all by itself, but I changed the
typeof because that's more correct and fixes some of the warnings by
itself.
What it can't fix is things like (from include/linux/pagemap.h):
volatile char c;
ret = __get_user(c, uaddr);
We unavoidably lose the volatile because we can't know it was there,
so the (void *) cast seems necessary in this case.
Looking at this some more, it seems like most of the complexity could
go away. I think I was avoiding any assignment to the target variable
until I knew that the copy_from_user had succeeded. I think that was
being too paranoid, and just copy_from_user straight into x should be
fine.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-23 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 19:31 [uml-devel] Real fix for rejected patch uaccess-warning Blaisorblade
2006-03-09 16:57 ` Jeff Dike
2006-03-10 15:22 ` Blaisorblade
2006-03-23 20:58 ` Jeff Dike [this message]
2006-03-23 23:52 ` Blaisorblade
2006-03-24 1:54 ` Jeff Dike
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=20060323205845.GA6109@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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