From: "yanmin dot zhang at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2452] kretprobe spinlock recursive remove
Date: Mon, 13 Mar 2006 09:11:00 -0000 [thread overview]
Message-ID: <20060313091055.7108.qmail@sourceware.org> (raw)
In-Reply-To: <20060313062327.2452.bibo.mao@intel.com>
------- Additional Comments From yanmin dot zhang at intel dot com 2006-03-13 09:10 -------
Sorry, the second approach has a problem. When trampline_handler is entered,
it must execute the corresponding kret handler.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2452
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-03-13 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 6:23 [Bug kprobes/2452] New: " bibo dot mao at intel dot com
2006-03-13 8:28 ` [Bug kprobes/2452] " yanmin dot zhang at intel dot com
2006-03-13 8:49 ` yanmin dot zhang at intel dot com
2006-03-13 9:11 ` yanmin dot zhang at intel dot com [this message]
2006-03-16 21:52 ` jkenisto at us dot ibm dot com
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=20060313091055.7108.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).