linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: akpm@linux-foundation.org
Cc: linuxppc-dev@ozlabs.org, carll@us.ibm.com, paulus@samba.org,
	cel@us.ibm.com
Subject: Re: [patch 1/5] powerpc: fix for OProfile callgraph for Power 64 bit user apps
Date: Tue, 10 Jun 2008 09:41:17 +1000	[thread overview]
Message-ID: <1213054877.25745.11.camel@pasglop> (raw)
In-Reply-To: <200806092326.m59NQ7rM014218@imap1.linux-foundation.org>

On Mon, 2008-06-09 at 16:26 -0700, akpm@linux-foundation.org wrote:
> From: Carl Love <cel@us.ibm.com>
> 
> Fix the 64 bit user code backtrace which currently may hang the system.
> 
> Signed-off-by: Carl Love <carll@us.ibm.com>
> Cc: Maynard Johnson <maynardj@us.ibm.com>

That looks weird. I doubt it's the right fix for the problem. Paul,
I remember this was discussed earlier, did we come up with a proper fix
already ?

Cheers,
Ben.

> On Thu, 15 May 2008 10:20:44 +1000
> Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > __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.
> > 
> > The old code copied 24 bytes from sp, and the new code copies 8 bytes
> > from sp and 8 bytes from sp + 16 - so I don't see where the 48 bytes
> > comes in to it?
> > 
> > \ufeffAlso the comment is a little hard to parse, I think you mean "Issue:
> > the ..", but I read "Issue" as a verb in that sentence. And "Don't read
> > more then" should be "than".
> 
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  arch/powerpc/oprofile/backtrace.c |   33 ++++++++++++++++++++++------
>  1 file changed, 27 insertions(+), 6 deletions(-)
> 
> diff -puN arch/powerpc/oprofile/backtrace.c~powerpc-fix-for-oprofile-callgraph-for-power-64-bit-user-apps arch/powerpc/oprofile/backtrace.c
> --- a/arch/powerpc/oprofile/backtrace.c~powerpc-fix-for-oprofile-callgraph-for-power-64-bit-user-apps
> +++ a/arch/powerpc/oprofile/backtrace.c
> @@ -53,19 +53,40 @@ static unsigned int user_getsp32(unsigne
>  #ifdef CONFIG_PPC64
>  static unsigned long user_getsp64(unsigned long sp, int is_first)
>  {
> -	unsigned long stack_frame[3];
> +	unsigned long stk_frm_lr;
> +	unsigned long stk_frm_sp;
> +	unsigned long size;
> +
> +	/* Issue the __copy_from_user_inatomic() third argument currently
> +	 * only takes sizes 1, 2, 4 or 8 bytes.  Don't read more then the
> +	 * first 48 bytes of the stack frame.  That is all that is
> +	 * guaranteed to exist.  Reading more may cause the system to hang.
> +	 *
> +	 * 64 bit stack frame layout:
> +	 * 0-7   bytes is the pointer to previous stack
> +	 * 8-15  bytes condition register save area
> +	 * 16-23 bytes link register save area
> +	 */
> +	size = sizeof(unsigned long);
> +	if (!access_ok(VERIFY_READ, (void __user *)sp, size))
> +		return 0;
>  
> -	if (!access_ok(VERIFY_READ, (void __user *)sp, sizeof(stack_frame)))
> +	if (__copy_from_user_inatomic(&stk_frm_sp, (void __user *)sp,
> +					size))
>  		return 0;
>  
> -	if (__copy_from_user_inatomic(stack_frame, (void __user *)sp,
> -					sizeof(stack_frame)))
> +	/* get the LR from the user stack */
> +	if (!access_ok(VERIFY_READ, (void __user *)(sp+16), size))
> +		return 0;
> +
> +	if (__copy_from_user_inatomic(&stk_frm_lr, (void __user *)(sp+16),
> +					size))
>  		return 0;
>  
>  	if (!is_first)
> -		oprofile_add_trace(STACK_LR64(stack_frame));
> +		oprofile_add_trace(stk_frm_lr);
>  
> -	return STACK_SP(stack_frame);
> +	return stk_frm_sp;
>  }
>  #endif
>  
> _
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

  reply	other threads:[~2008-06-09 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 23:26 [patch 1/5] powerpc: fix for OProfile callgraph for Power 64 bit user apps akpm
2008-06-09 23:41 ` Benjamin Herrenschmidt [this message]
2008-06-10  0:30   ` Michael Ellerman
2008-06-10 15:35     ` Carl Love
2008-06-10  0:21 ` 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=1213054877.25745.11.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=akpm@linux-foundation.org \
    --cc=carll@us.ibm.com \
    --cc=cel@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).