From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13074] New: Some nfs tapset probes broken under linux 3.1-rc1
Date: Thu, 11 Aug 2011 09:39:00 -0000 [thread overview]
Message-ID: <bug-13074-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13074
Bug #: 13074
Summary: Some nfs tapset probes broken under linux 3.1-rc1
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
The following failures can be seen under 3.1.0-0.rc1.git1.1.fc17.x86_64:
Running /home/mark/src/systemtap/testsuite/buildok/nfs_proc-detailed.stp
starting /home/mark/src/systemtap/testsuite/buildok/nfs_proc-detailed.stp
spawn1 stap -p4
/home/mark/src/systemtap/testsuite/buildok/nfs_proc-detailed.stp
spawn stap -p4 /home/mark/src/systemtap/testsuite/buildok/nfs_proc-detailed.stp
semantic error: unable to find local 'task' near pc 0x7e5ee in nfs_read_done
f
s/nfs/proc.c ( (alternatives: $data): identifier '$task' at
/usr/local/install/s
ystemtap/share/systemtap/tapset/nfs_proc.stp:803:11
source: status = $task->tk_status
semantic error: unable to find local 'task' near
p
c 0x7e5ee in nfs_read_done fs/nfs/proc.c ( (alternatives: $data): identifier
'
$task' at
/usr/local/install/systemtap/share/systemtap/tapset/nfs_proc.stp:803:1
1
source: status = $task->tk_status
^
semantic error: unable to find local 'task' near pc 0x7e578 in nfs_write_done
fs/nfs/proc.c ( (alternatives: $data): identifier '$task' at :1039:11
source: status = $task->tk_status
^
^
semantic error: unable to find local 'task' near pc 0x7e578 in nfs_write_done
fs/nfs/proc.c ( (alternatives: $data): identifier '$task' at :1039:11
source: status = $task->tk_status
^
semantic error: unable to find local 'task' near pc 0x848c0 in
nfs3_write_done fs/nfs/nfs3proc.c ( (alternatives: $data): identifier '$task'
at :1070:11
source: status = $task->tk_status
^
semantic error: unable to find local 'task' near pc 0x848c0 in
nfs3_write_done fs/nfs/nfs3proc.c ( (alternatives: $data): identifier '$task'
at :1070:11
source: status = $task->tk_status
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 571 exp19 0 1
FAIL: buildok/nfs_proc-detailed.stp
Running /home/mark/src/systemtap/testsuite/buildok/nfsd-all-probes.stp
starting /home/mark/src/systemtap/testsuite/buildok/nfsd-all-probes.stp
spawn1 stap -wp4 /home/mark/src/systemtap/testsuite/buildok/nfsd-all-probes.stp
spawn stap -wp4 /home/mark/src/systemtap/testsuite/buildok/nfsd-all-probes.stp
semantic error: no match while resolving probe point nfsd.createv3
semantic error: no match while resolving probe point nfsd.createv3
semantic error: no match while resolving probe point nfsd.createv3.return
semantic error: no match while resolving probe point nfsd.createv3.return
Pass 2: analysis failed. Try again with another '--vp 01' option.
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 770 exp19 0 1
FAIL: buildok/nfsd-all-probes.stp
Running /home/mark/src/systemtap/testsuite/buildok/nfsd-detailed.stp
starting /home/mark/src/systemtap/testsuite/buildok/nfsd-detailed.stp
spawn1 stap -p4 /home/mark/src/systemtap/testsuite/buildok/nfsd-detailed.stp
spawn stap -p4 /home/mark/src/systemtap/testsuite/buildok/nfsd-detailed.stp
semantic error: no match while resolving probe point nfsd.createv3
semantic error: no match while resolving probe point nfsd.createv3.return
semantic error: no match while resolving probe point nfsd.createv3
semantic error: no match while resolving probe point nfsd.createv3.return
Pass 2: analysis failed. Try again with another '--vp 01' option.
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 774 exp19 0 1
FAIL: buildok/nfsd-detailed.stp
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-11 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 9:39 mjw at redhat dot com [this message]
2011-08-11 20:42 ` [Bug tapsets/13074] " dsmith at redhat dot com
2011-08-15 13:18 ` mjw at redhat dot com
2013-01-10 19:52 ` dsmith at redhat dot com
2013-01-11 21:48 ` mjw at redhat dot com
2013-01-11 22:42 ` dsmith at redhat dot com
2013-01-11 22:59 ` mjw at redhat dot com
2017-05-08 20:38 ` fche 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-13074-6586@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).