From: "bibo dot mao at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2071] Probes on ISR with probes on task thread's prehandler crash the system
Date: Wed, 28 Dec 2005 06:13:00 -0000 [thread overview]
Message-ID: <20051227034121.8224.qmail@sourceware.org> (raw)
In-Reply-To: <20051220073112.2071.anil.s.keshavamurthy@intel.com>
------- Additional Comments From bibo dot mao at intel dot com 2005-12-27 03:41 -------
In linux 2.6.15-RC5-mm3, it does not crash in IA32, when running in EM64T, I
find that when there is int3 instruction in the first int3 hanlder function,
the first int 3 handler function can continue to execute, but when this
funciton return, system will crash.
For example, when kp_pre() in mon_sched.c calls
my_test_reentrant_export_function function which has been probed,
my_test_reentrant_export_function can continue to execute,but when it returned
system crashed.
And I think maybe it is the problem of trap stack in EM64T, I do not know how
trap stack is established when trap happens in use/kenrel mode or trap
executing mode.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2071
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2005-12-27 3:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 7:34 [Bug kprobes/2071] New: " anil dot s dot keshavamurthy at intel dot com
2005-12-20 9:40 ` [Bug kprobes/2071] " anil dot s dot keshavamurthy at intel dot com
2005-12-21 18:17 ` hien at us dot ibm dot com
2005-12-22 2:26 ` hien at us dot ibm dot com
2005-12-27 3:41 ` bibo dot mao at intel dot com
2005-12-28 6:13 ` bibo dot mao at intel dot com [this message]
2005-12-30 9:44 ` bibo dot mao at intel dot com
2006-01-13 2:08 ` anil dot s dot keshavamurthy at intel dot com
2006-01-13 2:14 ` anil dot s dot keshavamurthy at intel dot com
2006-01-13 2:15 ` anil dot s dot keshavamurthy at intel dot com
2006-01-13 4:42 ` bibo dot mao at intel dot com
2006-01-13 17:37 ` hien at us dot ibm dot com
2006-01-13 19:23 ` anil dot s dot keshavamurthy at intel dot com
2006-01-13 23:00 ` hien at us dot ibm dot com
2006-01-14 0:55 ` hien at us dot ibm dot com
2006-01-16 21:14 ` jkenisto at us dot ibm dot com
2006-12-11 19:34 ` fche at redhat dot com
2007-06-11 12:07 ` srikar at linux dot vnet dot ibm dot com
2007-06-11 16:14 ` jkenisto at us dot ibm dot com
2007-06-11 16:43 ` anil dot s dot keshavamurthy at intel dot com
2008-01-17 14:54 ` mhiramat at redhat dot com
2008-01-17 21:56 ` mhiramat at redhat dot com
2008-01-17 21:57 ` mhiramat at redhat dot com
2008-01-17 21:58 ` mhiramat at redhat dot com
2008-01-18 3:30 ` shaohua dot li at intel dot com
2008-01-21 22:47 ` mhiramat at redhat dot com
2008-03-13 15:00 ` mhiramat at redhat 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=20051227034121.8224.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).