From: "bill at broadley dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28958] New: Current git + RHEL (4.18.0) has 3 working NFSd examples, and one broken.
Date: Fri, 11 Mar 2022 19:06:43 +0000 [thread overview]
Message-ID: <bug-28958-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28958
Bug ID: 28958
Summary: Current git + RHEL (4.18.0) has 3 working NFSd
examples, and one broken.
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: bill at broadley dot org
Target Milestone: ---
I did a git clone today (Mar 11th, 2022) and nfsd-recent.stp, nfsdtop.std, and
nfsd_unlik.stp work (in testsuite/systemtap.examples/network).
However nfsd-trace.stp results in:
# /nopt/apps/systemtap-git-2022-03-11/bin/stap nfsd-trace.stp
Fri Mar 11 12:03:39 2022 MST 192.168.12.20:34051 nfsd.proc4.write 932,0 ERROR:
read fault [man error::fault] at 0x10 near operator '->' at
/nopt/nrel/apps/systemtap-2022-03-11/share/systemtap/tapset/linux/dentry.stp:267:19
WARNING: Number of errors: 1, skipped probes: 1
WARNING: /nopt/nrel/apps/systemtap-2022-03-11/bin/staprun exited with status: 1
Pass 5: run failed. [man error::pass5]
Here's the version:
[root@nas-1-0 network]# /nopt/nrel/apps/systemtap-2022-03-11/bin/stap -V
Systemtap translator/driver (version 4.7/0.185, commit
release-4.6-58-gaa27023c941f + changes)
Copyright (C) 2005-2021 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 5.17.0-rc4
enabled features: BPF NLS
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-11 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:06 bill at broadley dot org [this message]
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
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@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).