public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2453] kernel panic when probe elv_dequeue_request
Date: Thu, 16 Mar 2006 00:30:00 -0000	[thread overview]
Message-ID: <20060316003035.5409.qmail@sourceware.org> (raw)
In-Reply-To: <20060313083449.2453.guanglei@cn.ibm.com>


------- Additional Comments From jkenisto at us dot ibm dot com  2006-03-16 00:30 -------
Some questions come to mind:
a. Do we see the BUG only when there's a probepoint on elv_dequeue_request?
b. Is single-stepping the tdnei instruction somehow causing the BUG?
c. Should we be allowing probepoints on tdnei instructions?
d. Is the tdnei instruction really the first instruction after the function
prolog?  (This would make a difference if (b) or (c) comes into play.)

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |ananth at in dot ibm dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


http://sourceware.org/bugzilla/show_bug.cgi?id=2453

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2006-03-16  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  8:34 [Bug kprobes/2453] New: " guanglei at cn dot ibm dot com
2006-03-13 14:49 ` [Bug kprobes/2453] " fche at redhat dot com
2006-03-14  4:27   ` Ananth N Mavinakayanahalli
2006-03-14  4:27 ` ananth at in dot ibm dot com
2006-03-16  0:30 ` jkenisto at us dot ibm dot com [this message]
2006-03-16  3:18   ` Michael Ellerman

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=20060316003035.5409.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).