From: Huang Ying <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gcosta@redhat.com" <gcosta@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: + drivers-acpi-apei-erst-dbgc-get_useru64-doesnt-work-on-i386.patch added to -mm tree
Date: Thu, 12 Aug 2010 08:42:31 +0800 [thread overview]
Message-ID: <1281573751.2744.1415.camel@yhuang-dev> (raw)
In-Reply-To: <20100811173327.3ae325ff.akpm@linux-foundation.org>
On Thu, 2010-08-12 at 08:33 +0800, Andrew Morton wrote:
> On Wed, 11 Aug 2010 16:43:10 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > On Wed, 11 Aug 2010 16:06:24 -0700 akpm@linux-foundation.org wrote:
> >
> > >
> > > The patch titled
> > > drivers/acpi/apei/erst-dbg.c: get_user(u64) doesn't work on i386
> > > has been added to the -mm tree. Its filename is
> > > drivers-acpi-apei-erst-dbgc-get_useru64-doesnt-work-on-i386.patch
> > >
> > > Before you just go and hit "reply", please:
> > > a) Consider who else should be cc'ed
> > > b) Prefer to cc a suitable mailing list as well
> > > c) Ideally: find the original patch on the mailing list and do a
> > > reply-to-all to that, adding suitable additional cc's
> > >
> > > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> > >
> > > See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> > > out what to do about this
> > >
> > > The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> > >
> > > ------------------------------------------------------
> > > Subject: drivers/acpi/apei/erst-dbg.c: get_user(u64) doesn't work on i386
> > > From: Andrew Morton <akpm@linux-foundation.org>
> > >
> > > Might be an x86 bug? A get_user() on a u64 on i386 expands to
> > >
> > > #define __get_user_8(__ret_gu, __val_gu, ptr) \
> > > __get_user_x(X, __ret_gu, __val_gu, ptr)
> > >
> > > which emits a call to __get_user_X(), which doesn't exist.
> > >
> > > Kludge around it with copy_from_user().
> > >
> >
> > Reported and fixed yesterday.
>
> Not very well.
>
> + rc = copy_from_user(&record_id, (void __user *)arg,
> + sizeof(u64));
>
> better to use sizeof(record_id).
Will fix this with a new version. And the ssize printk format string.
> Where's Len??
>
> Anyway, this should be fixed in x86 core, I suspect.
Yes. I think so too.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2010-08-12 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201008112336.o7BNaNEj020805@imap1.linux-foundation.org>
2010-08-11 23:43 ` + drivers-acpi-apei-erst-dbgc-get_useru64-doesnt-work-on-i386.patch added to -mm tree Randy Dunlap
2010-08-12 0:33 ` Andrew Morton
2010-08-12 0:42 ` Huang Ying [this message]
2010-08-12 1:35 ` H. Peter Anvin
2010-08-12 4:22 ` H. Peter Anvin
2010-08-12 4:30 ` Andrew Morton
2010-08-12 4:42 ` H. Peter Anvin
2010-08-12 5:06 ` H. Peter Anvin
2010-08-12 6:03 ` Andrew Morton
2010-08-12 6:10 ` H. Peter Anvin
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=1281573751.2744.1415.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=gcosta@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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