public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "bill at broadley dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28394] New: Systemtap 4.6 on Centos 8.4/4.18 kernel died in nfsd-trace example
Date: Tue, 28 Sep 2021 20:17:12 +0000	[thread overview]
Message-ID: <bug-28394-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28394

            Bug ID: 28394
           Summary: Systemtap 4.6 on Centos 8.4/4.18 kernel died in
                    nfsd-trace example
           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 tried the Systemtap on Rocky-8.4 (a recompile of RHEL-8.4) *AND* with the
current git branch and tried the nfsd-trace example.

Kernel/Env:

[root@nas-1-0 systemtap]# uname -a
Linux nas-1-0 4.18.0-305.19.1.el8_4.x86_64 #1 SMP Wed Sep 15 19:12:32 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
[root@nas-1-0 systemtap]# stap-prep 
Configuring for kernel release 4.18.0-305.19.1.el8_4.x86_64
[root@nas-1-0 systemtap]#

Rocky-8.4/RHEL-8.4 provided systemtap:

[root@nas-1-0 systemtap]# /usr/bin/stap --version
Systemtap translator/driver (version 4.4/0.182, rpm 4.4-11.el8_4.0.1)
With the Rocky-8.4/RHEL-8.4 provided stap:

[root@nas-1-0 systemtap]# /usr/bin/stap
./testsuite/systemtap.examples/network/nfsd-trace.stp
WARNING: Potential type mismatch in reassignment: identifier 'root_dentry' at
/usr/share/systemtap/tapset/linux/dentry.stp:246:3
 source:                root_dentry = @cast(task, "task_struct",
"kernel")->fs->root->dentry
                        ^
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/usr/share/systemtap/tapset/linux/dentry.stp:267:19
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/usr/share/systemtap/tapset/linux/dentry.stp:267:19
Tue Sep 28 14:08:57 2021 MDT 192.168.1.46:24323 nfsd.proc4.write 1851,409600
Tue Sep 28 14:08:57 2021 MDT 192.168.1.46:24323 nfsd.proc4.write 106,25476458
WARNING: Number of errors: 2, skipped probes: 2
WARNING: /usr/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
Number of similar warning messages suppressed: 659.
Rerun with -v to see them.

With the git download from today:

[root@nas-1-0 systemtap]# ./stap --version
Systemtap translator/driver (version 4.6/0.182, commit release-4.5-87-
gb367613c3bb8 + changes)

[root@nas-1-0 systemtap]# ./stap
./testsuite/systemtap.examples/network/nfsd-trace.stp
WARNING: Potential type mismatch in reassignment: identifier 'root_dentry' at
/nopt/nrel/apps/systemtap-2021-09-23/share/systemtap/tapset/linux/dentry.stp:246:3
 source:                root_dentry = @cast(task, "task_struct",
"kernel")->fs->root->dentry
                        ^
Tue Sep 28 14:10:47 2021 MDT 192.168.1.75:52994 nfsd.proc4.write 2592,286720
Tue Sep 28 14:10:47 2021 MDT 192.168.1.75:52994 nfsd.proc4.write 4265,53248
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/nopt/nrel/apps/systemtap-2021-09-23/share/systemtap/tapset/linux/dentry.stp:267:19
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/nopt/nrel/apps/systemtap-2021-09-23/share/systemtap/tapset/linux/dentry.stp:267:19
WARNING: Number of errors: 2, skipped probes: 2
WARNING: /nopt/nrel/apps/systemtap-2021-09-23/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
Number of similar warning messages suppressed: 659.
Rerun with -v to see them.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-09-28 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 20:17 bill at broadley dot org [this message]
2022-03-11 19:00 ` [Bug runtime/28394] " bill at broadley dot org

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-28394-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).