public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: dsmith at redhat dot com <sourceware-bugzilla@sourceware.org>
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug runtime/3379] probe on "atomic_notifier_call_chain" crashes the system
Date: Wed, 18 Oct 2006 21:48:00 -0000	[thread overview]
Message-ID: <20061018142841.B27693@unix-os.sc.intel.com> (raw)
In-Reply-To: <20061018191129.345.qmail@sourceware.org>; from sourceware-bugzilla@sourceware.org on Wed, Oct 18, 2006 at 07:11:29PM -0000

On Wed, Oct 18, 2006 at 07:11:29PM -0000, dsmith at redhat dot com wrote:
> 
> Bibo Mao volunteered to add kernel patches for the 3 problem areas I found. 
> Here's the specific one for atomic_notifier_call_chain(), which marks it with
> "__kprobes":
> 
> <http://www.ussg.iu.edu/hypermail/linux/kernel/0609.3/0589.html>

BTW, today I ran the 
stap -vv -e 'probe kernel.function("*") { log(".") }' on i386 box running
2.6.19-rc2-git2 and I had no issues. I even was able to do ls -l though the
system was on its knees. I had left this running for ~10 minutes before I killed
(and the stap module got unloaded cleanly).

> 
> A problem we have is that atomic_notifier_call_chain() has been marked as
> "__kprobes" in the upstream kernel, but hasn't made it to a released kernel from
> my understanding (by either kernel.org or a vendor).
Yup, this is in upstream kernel.

> 
> I have no problem with adding "atomic_notifier_call_chain" to the blacklist in
> the meantime.
We need this in any case as the systemtap could be run on older version of the kernel too.

-Anil Keshavamurthy

  reply	other threads:[~2006-10-18 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  7:31 [Bug runtime/3379] New: " guij at cn dot ibm dot com
2006-10-18 19:11 ` [Bug runtime/3379] " dsmith at redhat dot com
2006-10-18 21:48   ` Keshavamurthy Anil S [this message]
2006-10-18 21:48 ` anil dot s dot keshavamurthy at intel dot com
2006-10-24 14:56 ` dsmith 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=20061018142841.B27693@unix-os.sc.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=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).