From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/28958] Current git + RHEL (4.18.0) has 3 working NFSd examples, and one broken.
Date: Tue, 22 Mar 2022 17:55:18 +0000 [thread overview]
Message-ID: <bug-28958-6586-ajhQW1Vo7l@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28958-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28958
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from William Cohen <wcohen at redhat dot com> ---
This has been fixed by commit 3739d47c4cc427ce4818d884f429a3efa85c38ae
An example of nfsd-tracing.stp running correctly on a rhel8 vm:
$ sudo ../install/bin/stap testsuite/systemtap.examples/network/nfsd-trace.stp
Tue Mar 22 13:51:51 2022 EDT 192.168.122.253:64003 nfsd.proc4.read 13,0
/mnt/myshareddir/testing
Tue Mar 22 13:51:51 2022 EDT 192.168.122.253:64003 nfsd.proc4.lookup .#testing
/mnt/myshareddir/.#testing
Tue Mar 22 13:51:51 2022 EDT 192.168.122.253:64003 nfsd.proc4.lookup #testing#
/mnt/myshareddir/#testing#
...
Also get the expected result for task_paths.stp now:
$ sudo ../install/bin/stap testsuite/systemtap.base/task_paths.stp -T 1
current cwd: /home/wcohen/systemtap_write/systemtap
current exe: /home/wcohen/systemtap_write/install/libexec/systemtap/stapio
ERROR: read fault [man error::fault] at 0x0
ERROR: read fault [man error::fault] at 0xffffffffffffffff
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-22 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:06 [Bug runtime/28958] New: " bill at broadley dot org
2022-03-11 19:08 ` [Bug runtime/28958] " bill at broadley dot org
2022-03-11 19:11 ` [Bug testsuite/28958] " bill at broadley dot org
2022-03-17 20:18 ` wcohen at redhat dot com
2022-03-17 21:49 ` bill at broadley dot org
2022-03-18 14:40 ` wcohen at redhat dot com
2022-03-18 15:18 ` wcohen at redhat dot com
2022-03-22 17:55 ` wcohen at redhat dot com [this message]
2022-03-25 18:22 ` bill at broadley dot org
2022-03-25 20:02 ` wcohen at redhat dot com
2022-03-25 22:27 ` bill at broadley dot org
2022-03-26 20:07 ` 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-28958-6586-ajhQW1Vo7l@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).