From: Matthew Ward <matthew.ward@fubra.com>
To: systemtap@sources.redhat.com
Subject: usertap kernel read faults - can I ignore them somehow?
Date: Tue, 29 Nov 2011 14:30:00 -0000 [thread overview]
Message-ID: <jb2pmt$is5$1@dough.gmane.org> (raw)
I'm having an issue with our usertap tapset
(https://github.com/fubralimited/usertap) on a high-load server where
trying to find an IP address for a particular socket is causing
systemtap to crash out on a kernel read fault. This tapset always builds
and runs on a low-traffic server, but after testing on one of our
high-traffic nodes it sometimes builds and runs without a problem, and
sometimes refuses to build at all.
There's a gist of the error we're getting here:
https://gist.github.com/1404868. The relevant line we're getting is:
ERROR: kernel read fault at 0x0000000100000264 (addr) near identifier
'@cast' at /usr/share/systemtap/tapset/ip.stp:45:11
I presume that that file is called/included by the usertap tapset as
it's asking for the IP address associated with a socket, but this seems
to be causing an error in certain situations (presumably where it's
requesting an IP address for something that doesn't have one). Is there
any way I can tell our systemtap script to silence or ignore the call
for the IP address if that lookup fails, so that it will start anyway
like it does normally?
System info:
systemtap-runtime-1.4-6.el6_1.2.x86_64
kernel-2.6.32-131.17.1.el6.x86_64
Source code for usertap:
https://github.com/fubralimited/usertap/blob/master/src/usertap.stp
---
Matthew Ward
e: matthew.ward@fubra.com
next reply other threads:[~2011-11-29 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:30 Matthew Ward [this message]
2011-11-29 14:38 ` Frank Ch. Eigler
2011-11-29 15:00 ` Matthew Ward
2011-11-29 15:02 ` Matthew Ward
2011-11-29 17:02 ` Frank Ch. Eigler
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='jb2pmt$is5$1@dough.gmane.org' \
--to=matthew.ward@fubra.com \
--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).