From: "guillaume at morinfr dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26184] New: fullpath_struct_file does not handle struct dentry on 5.6.19-300.fc32.x86_64
Date: Wed, 26 May 2021 21:26:50 +0000 [thread overview]
Message-ID: <bug-26184-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26184
Bug ID: 26184
Summary: fullpath_struct_file does not handle struct dentry on
5.6.19-300.fc32.x86_64
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: craig.ringer at 2ndquadrant dot com
CC: guillaume at morinfr dot org
Target Milestone: ---
CC: guillaume at morinfr dot org
Created attachment 12671
--> https://sourceware.org/bugzilla/attachment.cgi?id=12671&action=edit
Output from fullpath_struct_file
fullpath_struct_file fails in dentry.stp with "type definition 'dentry' not
found". Full error output will be provided as attachment.
Command:
$ stap -v -c /bin/false -e 'probe process.begin { printf("%s",
fullpath_struct_file(task_current(), current_exe_file())); exit(); }'
semantic error: type definition 'dentry' not found in '': operator '@cast' at
/usr/share/systemtap/tapset/linux/dentry.stp:64:15
source: s = & @cast(dentry, "dentry")->d_name;
... more errors ... (see attached)
$ uname -r
5.6.19-300.fc32.x86_64
$ rpm -q systemtap
systemtap-4.3-1.fc32.x86_64
$ stap --version
Systemtap translator/driver (version 4.3/0.179, rpm 4.3-1.fc32)
Copyright (C) 2005-2020 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 5.7.0
enabled features: AVAHI BOOST_STRING_REF DYNINST BPF JAVA PYTHON3 LIBRPM
LIBSQLITE3 LIBVIRT LIBXML2 NLS NSS READLINE MONITOR_LIBS
The failing command simplifies to:
$ stap -v -c /bin/false -e 'probe process.begin { printf("%s", d_name(0));
exit(); }'
--- Comment #1 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
*** Bug 26185 has been marked as a duplicate of this bug. ***
--- Comment #2 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
*** Bug 26186 has been marked as a duplicate of this bug. ***
--- Comment #3 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Checked latest git 403e92779, same outcome:
WARNING: Potential type mismatch in reassignment: identifier 'root_dentry' at
/usr/local/systemtap/share/systemtap/tapset/linux/dentry.stp:246:3
source: root_dentry = @cast(task, "task_struct",
"kernel")->fs->root->dentry
^
--- Comment #4 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Well, similar anyway; it runs, then dies with
ERROR: read fault [man error::fault] at 0x10 near operator '->' at
/usr/local/systemtap/share/systemtap/tapset/linux/dentry.stp:267:19
but the warnings from the latest git match the errors from the packaged
version.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-05-26 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 21:26 guillaume at morinfr dot org [this message]
2021-05-26 22:06 ` [Bug tapsets/26184] " guillaume at morinfr dot org
2022-03-22 18:15 ` wcohen 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-26184-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).