All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: venki kaps <venkiece2005@gmail.com>, Nicolas Pitre <nico@cam.org>,
	"sagar.abhishek@gmail.com" <sagar.abhishek@gmail.com>,
	"jkenisto@us.ibm.com" <jkenisto@us.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"prasanna@in.ibm.com" <prasanna@in.ibm.com>
Subject: Re: ARM + jprobes/kretprobes SEGV/hangs/OOPS in 2.6.29 kernel
Date: Tue, 1 Sep 2009 15:25:49 +0100	[thread overview]
Message-ID: <20090901142549.GA21501@flint.arm.linux.org.uk> (raw)
In-Reply-To: <tnxocpu7osx.fsf@pc1117.cambridge.arm.com>

On Tue, Sep 01, 2009 at 02:54:54PM +0100, Catalin Marinas wrote:
> venki kaps <venkiece2005@gmail.com> wrote:
> > I have found the exact problem with respect to ARM jprobes.
> >
> > The problem with configure i.e, CONFIG_ARM_UNWIND = y; is enabled.
> 
> I haven't followed the kprobes implementation for ARM but does it make
> any assumptions about the existence of a frame pointer on the stack?
> Enabling stack unwinding automatically disables the framepointer.

If it uses CALLER_ADDRESSx() then it won't work with unwinding enabled.
See 5613/1 (which is pending in the devel branch.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2009-09-01 14:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 10:42 ARM + jprobes/kretprobes SEGV/hangs/OOPS in 2.6.29 kernel venki kaps
2009-08-25 17:37 ` Nicolas Pitre
2009-08-31  5:27   ` venki kaps
2009-08-31 10:11     ` venki kaps
2009-09-01  6:55       ` venki kaps
2009-09-01 13:54         ` Catalin Marinas
2009-09-01 14:25           ` Russell King [this message]
2009-09-01 14:43             ` Catalin Marinas
2009-09-01 17:56               ` Nicolas Pitre
2009-09-16  9:40                 ` venki kaps

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=20090901142549.GA21501@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=catalin.marinas@arm.com \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=prasanna@in.ibm.com \
    --cc=sagar.abhishek@gmail.com \
    --cc=venkiece2005@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.