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 14:40:02 +0000 [thread overview]
Message-ID: <bug-28958-6586-et3CWxJXNn@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|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2022-03-18
Ever confirmed|0 |1
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
I am able to replicate error on RHEL8 vm exporting nfs file system:
$ sudo ../install/bin/stap -v
testsuite/systemtap.examples/network/nfsd-trace.stp
Pass 1: parsed user script and 483 library scripts using
294924virt/95612res/17928shr/79820data kb, in 180usr/160sys/485real ms.
Pass 2: analyzed script: 22 probes, 64 functions, 7 embeds, 1 global using
553136virt/351840res/19852shr/338032data kb, in 5550usr/1570sys/7502real ms.
Pass 3: translated to C into
"/tmp/stap13rEn4/stap_e2015f4beef9bcfacf31be2a7eccb277_61031_src.c" using
553136virt/351968res/19980shr/338032data kb, in 660usr/100sys/773real ms.
Pass 4: compiled C into "stap_e2015f4beef9bcfacf31be2a7eccb277_61031.ko" in
19610usr/3730sys/24872real ms.
Pass 5: starting run.
Fri Mar 18 10:30:25 2022 EDT 192.168.122.253:32771 nfsd.proc4.lookup testing
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/home/wcohen/systemtap_write/install/share/systemtap/tapset/linux/dentry.stp:267:19
WARNING: Number of errors: 1, skipped probes: 1
WARNING: /home/wcohen/systemtap_write/install/bin/staprun exited with status: 1
Pass 5: run completed in 20usr/250sys/52136real ms.
Pass 5: run failed. [man error::pass5]
The nfsd-trace.stp is the only using task_dentry_path
(https://sourceware.org/systemtap/tapsets/API-task-dentry-path.html).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-18 14:40 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 [this message]
2022-03-18 15:18 ` wcohen at redhat dot com
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-et3CWxJXNn@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).