From: Andrew Morton <akpm@osdl.org>
To: "Lynch, Rusty" <rusty.lynch@intel.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, prasadav@us.ibm.com,
hien@us.ibm.com, prasanna@in.ibm.com, jkenisto@us.ibm.com
Subject: Re: [patch] x86_64 specific function return probes
Date: Thu, 2 Jun 2005 22:07:29 -0700 [thread overview]
Message-ID: <20050602220729.762d9385.akpm@osdl.org> (raw)
In-Reply-To: <032EB457B9DBC540BFB1B7B519C78B0E07499229@orsmsx404.amr.corp.intel.com>
"Lynch, Rusty" <rusty.lynch@intel.com> wrote:
>
>
> From: Andi Kleen [mailto:ak@suse.de]
> >On Thu, Jun 02, 2005 at 09:09:09AM -0700, Rusty Lynch wrote:
> >> The following patch adds the x86_64 architecture specific
> implementation
> >> for function return probes to the 2.6.12-rc5-mm2 kernel.
> >
> >This is not a sufficient description for a patch. Can you describe
> >how it actually works and what it does?
> >
>
> Ok, let me write up a description and I'll repost.
You did, but:
> >> + * Called when we hit the probe point at kretprobe_trampoline
> >> + */
> >> +int trampoline_probe_handler(struct kprobe *p, struct pt_regs *regs)
> >> +{
> >> + struct task_struct *tsk;
> >> + struct kretprobe_instance *ri;
> >> + struct hlist_head *head;
> >> + struct hlist_node *node;
> >> + unsigned long *sara = (unsigned long *)regs->rsp - 1;
> >> +
> >> + tsk = arch_get_kprobe_task(sara);
> >
> >I dont think you handle the case of the exception happening on
> >a exception or interrupt stack. This is broken.
What about this problem?
next prev parent reply other threads:[~2005-06-03 5:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 17:35 [patch] x86_64 specific function return probes Lynch, Rusty
2005-06-03 5:07 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-03 16:54 Lynch, Rusty
2005-06-03 16:40 Lynch, Rusty
2005-06-03 16:45 ` Andi Kleen
2005-06-03 16:05 Lynch, Rusty
2005-06-02 20:58 Rusty Lynch
2005-06-03 15:45 ` Andi Kleen
2005-06-02 16:09 Rusty Lynch
2005-06-02 17:31 ` Andi Kleen
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=20050602220729.762d9385.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=hien@us.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasadav@us.ibm.com \
--cc=prasanna@in.ibm.com \
--cc=rusty.lynch@intel.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.