From: Carl Love <cel@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, akpm@linux-foundation.org, carll@us.ibm.com
Subject: Re: [patch 1/4] powerpc: fix for OProfile callgraph for Power 64 bit user apps
Date: Thu, 15 May 2008 07:50:08 -0700 [thread overview]
Message-ID: <1210863008.7726.129.camel@carll-linux-desktop> (raw)
In-Reply-To: <18475.46317.936165.577835@cargo.ozlabs.ibm.com>
On Thu, 2008-05-15 at 13:58 +1000, Paul Mackerras wrote:
> Michael Ellerman writes:
>
> > __copy_from_user_inatomic() accepts any value for n, it just has a
> > special case for 1, 2, 4 and 8 - but it should still work for other
> > values.
>
> There is a bug in __copy_from_user_inatomic that
>
> http://patchwork.ozlabs.org/linuxppc/patch?id=18418
>
> fixes, and I'm about to send that Linus-wards.
>
> Carl, to what extent does that fix eliminate the need for the changes
> in your patch?
>
> Paul.
Paul:
I will have to apply the above mentioned patch to see if it fixes the
issue. What I found was when the original code tried to copy three
unsigned long into stack_frame[3], i.e. 24 bytes my system consistently
failed. The comment about 48 bytes is a note that is all that is
guaranteed to be there according to the API. I found by restricting the
copy to the values in the case statement, things worked.
Carl Love
prev parent reply other threads:[~2008-05-15 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:12 [patch 1/4] powerpc: fix for OProfile callgraph for Power 64 bit user apps akpm
2008-05-15 0:20 ` Michael Ellerman
2008-05-15 3:58 ` Paul Mackerras
2008-05-15 14:50 ` Carl Love [this message]
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=1210863008.7726.129.camel@carll-linux-desktop \
--to=cel@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=carll@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).