From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15961] nd_syscall.exp failure on i686
Date: Thu, 17 Oct 2013 14:27:00 -0000 [thread overview]
Message-ID: <bug-15961-6586-kV5pLndSnw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15961-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15961
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
I'm seeing a similar failure elsewhere (RHEL5 on s390x), that is a bit more
intermittent. The failure is in the 64-bit mmap nd_syscall test.
A mmap call that was supposed to match the following regexp:
===
mmap: mmap[2]* \([x0-9a-fA-F]+, 1030, PROT_READ, MAP_SHARED, [\-0-9]+,
[x0-9a-fA-F]+\) = [x0-9a-fA-F]+
====
came out like this:
====
mmap: mmap (0x0, 0, PROT_NON, MAP_PRIVATE, 0, 1) = 0x20000004000
====
I couldn't figure out how it was so wrong until I looked at the nd_syscall.mmap
probe alias source:
====
probe nd_syscall.mmap = kprobe.function("old_mmap") ?,
kprobe.function("old32_mmap") ?,
kprobe.function("SyS_s390_old_mmap") ?
{
asmlinkage()
if ((symname(addr()) == "old_mmap") || (symname(addr()) ==
"SyS_s390_old_mmap"))
argstr = get_mmap_args(pointer_arg(1))
else
argstr = get_32mmap_args(pointer_arg(1))
}
====
If 'symname(addr())' fails, the probe defaults to using the 32-bit function,
which interpreted the 64-bit data as 32-bit data.
The following seems to fix the problem:
====
probe nd_syscall.mmap = __nd_syscall.mmap, __nd_syscall.mmap32
{
name = "mmap"
}
probe __nd_syscall.mmap = kprobe.function("old_mmap") ?,
kprobe.function("SyS_s390_old_mmap") ?
{
asmlinkage()
argstr = get_mmap_args(pointer_arg(1))
}
probe __nd_syscall.mmap32 = kprobe.function("old32_mmap") ?
{
asmlinkage()
argstr = get_32mmap_args(pointer_arg(1))
}
====
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-10-17 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 21:30 [Bug tapsets/15961] New: " dsmith at redhat dot com
2013-10-17 14:27 ` dsmith at redhat dot com [this message]
2013-10-17 21:25 ` [Bug tapsets/15961] " 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=bug-15961-6586-kV5pLndSnw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).