From: Masami Hiramatsu <mhiramat@redhat.com>
To: Abhishek Sagar <sagar.abhishek@gmail.com>
Cc: ananth@in.ibm.com, LKML <linux-kernel@vger.kernel.org>,
jkenisto@us.ibm.com, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/3][RFC] x86: Catch stray non-kprobe breakpoints
Date: Tue, 29 Jan 2008 10:13:21 -0500 [thread overview]
Message-ID: <479F4291.1060106@redhat.com> (raw)
In-Reply-To: <863e9df20801290240t6c724cb9x145fd6b1ca4f3c78@mail.gmail.com>
Abhishek Sagar wrote:
> Placing a breakpoint on kprobe_handler (say) can loop into a recursive
> trap without allowing the debugger's notifier chain to be invoked. I'm
> assuming that non-kprobe exception notifiers may (or even should) run
> after kprobe's notifier callback (kprobe_exceptions_notify).
In that case, why don't you just reduce the priority of kprobe_exceptions_nb?
Then, the execution path becomes very simple.
int3 (non-kprobe) -> do_int3 -> non-krpobe/debugger
I also like to use a debugger for debugging kprobes. that will help us.
Best Regards,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2008-01-29 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 9:08 [PATCH 0/3][RFC] x86: Catch stray non-kprobe breakpoints Abhishek Sagar
2008-01-29 6:02 ` Ananth N Mavinakayanahalli
2008-01-29 10:40 ` Abhishek Sagar
2008-01-29 13:18 ` Ananth N Mavinakayanahalli
2008-01-29 17:24 ` Abhishek Sagar
2008-01-29 15:13 ` Masami Hiramatsu [this message]
2008-01-29 18:08 ` Abhishek Sagar
2008-01-29 19:29 ` Masami Hiramatsu
2008-01-30 4:07 ` Ananth N Mavinakayanahalli
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=479F4291.1060106@redhat.com \
--to=mhiramat@redhat.com \
--cc=ananth@in.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sagar.abhishek@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.