linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Franz Sirl <Franz.Sirl-ppc@lauterbach.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Miles Lane <miles.lane@comcast.net>,
	linuxppc-dev@lists.linuxppc.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: linuxppc-2.5 (rsync mvista) -- drivers/input/evdev.c:243: error: invalid lvalue in asm statement
Date: 04 Aug 2003 11:42:21 +0200	[thread overview]
Message-ID: <1059990141.3232.1.camel@gaston> (raw)
In-Reply-To: <5.2.1.1.2.20030804104557.01f0fe00@mail.lauterbach.com>


On Mon, 2003-08-04 at 10:49, Franz Sirl wrote:
> >
> >No Paul, it's not your fault, if you look closely at evdev, that code
> >can't really work properly anyway.
>
> Well, his patch to get_user exposed it, but the bug is really in the very
> questionable use of the gcc extension to accept ?: expressions as lvalue,
> see <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11564>
>
> >I talked to Vojtech at OLS and he'll be fixing that to always pass
> >either an u32 or an int to userspace.
>
> I've sent him a patch too as a result of the above GCC PR.

It's still totally wrong to access userland with a variable sized
data since my understanding is that userland doesn't know what size
the kernel will use for access here, thus it works for little endian
but not big endian (well... afaik).

Vojtech and I agreed that this should be changed into uniform use
of a single sized type (u32 or int) that gets only converted in
the kernel.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-08-04  9:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  1:23 linuxppc-2.5 (rsync mvista) -- drivers/input/evdev.c:243: error: invalid lvalue in asm statement Miles Lane
2003-08-03  9:13 ` Benjamin Herrenschmidt
2003-08-03 11:23 ` Paul Mackerras
2003-08-03 11:31   ` Benjamin Herrenschmidt
2003-08-04  8:49     ` Franz Sirl
2003-08-04  9:42       ` Benjamin Herrenschmidt [this message]
2003-08-04 11:24         ` Paul Mackerras

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=1059990141.3232.1.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=Franz.Sirl-ppc@lauterbach.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=miles.lane@comcast.net \
    --cc=paulus@samba.org \
    --cc=vojtech@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).