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: Fri, 18 Mar 2022 15:18:39 +0000 [thread overview]
Message-ID: <bug-28958-6586-P393AvCdd7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28958-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28958
--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Found other testsuite scripts that end up using task_dentry_path directly and
indirectly:
systemtap.examples/network/autofs4.stp
systemtap.examples/process/pfiles.stp
systemtap.base/task_paths.stp
systemtap.base/task_fd_lookup.stp
Of these the task_paths.stp is the simplest and looks to be exhibiting the same
behavior. Note that the last two ERROR messages are expected and correct, but
the first two should print out strings:
$ sudo ../../install/bin/stap systemtap.base/task_paths.stp -T 1
ERROR: read fault [man error::fault] at 0x10
ERROR: read fault [man error::fault] at 0x10
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-18 15:18 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 [this message]
2022-03-22 17:55 ` wcohen at redhat dot com
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-P393AvCdd7@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).