From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/5150] buildok/nfs-all-probes.stp fails
Date: Mon, 09 Nov 2009 16:00:00 -0000 [thread overview]
Message-ID: <20091109160012.20183.qmail@sourceware.org> (raw)
In-Reply-To: <20071009153328.5150.wcohen@redhat.com>
------- Additional Comments From dsmith at redhat dot com 2009-11-09 16:00 -------
(Here's some info copied over from bug #10900 with up-to-date testing results.)
There are several problems in the nfs tapset. During testing I used:
- a x86_64 rhel5 system (kernel 2.6.18-164.2.1.el5)
- a ia64 rhel5 system (kernel 2.6.18-157.el5)
- a rawhide system (kernel 2.6.31.5-96.fc12.x86_64.debug).
- probes 'nfs.fop.fsync' & 'nfs.fop.fsync.return' didn't work on rawhide
- probes 'nfs.fop.sendfile' & 'nfs.fop.sendfile.return' didn't work on rawhide
- probes 'nfs.fop.check_flags' & 'nfs.fop.check_flags.return' don't work on
either ia64 rhel5 or rawhide. They did work on the x86_64 rhel5 system.
- probe 'nfs.aop.readpages.return' has a mistake in it. 'size = retstr' should
be 'size = $return' (to match the other return probes)
- probes 'nfs.aop.prepare_write' & 'nfs.aop.prepare_write.return' don't work on
either rhel5 or rawhide
- probes 'nfs.aop.commit_write' & 'nfs.aop.commit_write.return' don't work on
either rhel5 or rawhide
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5150
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-11-09 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 15:33 [Bug tapsets/5150] New: " wcohen at redhat dot com
2007-10-09 16:53 ` [Bug tapsets/5150] " mmlnx at us dot ibm dot com
2009-11-09 15:58 ` dsmith at redhat dot com
2009-11-09 16:00 ` dsmith at redhat dot com [this message]
2009-11-16 19:01 ` 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=20091109160012.20183.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).