Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Hello. One of my test just uses:
# diskdevstat 5 60
which fails
Version-Release number of selected component (if applicable):
# rpm -qf /usr/share/systemtap/tapset/linux/vfs.stp
systemtap-client-4.1-3.el8.x86_64
systemtap-devel-4.1-3.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1. run diskdevstat 5 60
3.
Actual results:
semantic error: failed to retrieve location attribute for 'file' [man error::dwarf]: identifier '$file' at /usr/share/systemtap/tapset/linux/vfs.stp:1055:19
dieoffset: 0x36a4919 from /usr/lib/debug/lib/modules/4.18.0-107.el8.x86_64/vmlinux
function: vfs_write at fs/read_write.c:546:3 inlined by vfs_write at fs/read_write.c:533:9
source: dev = __file_dev($file)
^
semantic error: unresolved type : identifier '$file' at :1055:19
source: dev = __file_dev($file)
^
Pass 2: analysis failed. [man error::pass2]
Number of similar error messages suppressed: 6.
Rerun with -v to see them.
Expected results:
no error? :)
Additional info:
This feels like a dwarf quality problem (of bz1652740 type). Some of them are work-aroundble using prologue-searching (stap -P). Where does your diskdevstat come from? Not sure what that actually is. It doesn't look like a part of systemtap (examples), neither it seems to be a packaged binary installing to /usr/bin/.
Ah I see the stap & kernel versions up there.
The kernel version is beyond 4.18.0-85, which was the first one affected by a gcc rebase (8.2.1->8.3.1). Could be a dupe of bug #1709831.
Robin, thanks. I was missing that this stap script comes from tuned-utils-systemtap.
(Any idea why don't we just include those as systemtap sample scripts?)
With the 4.18.0-172.el8 kernel, this now passes. Suggesting CLOSED/CURRENTRELEASE.
Description of problem: Hello. One of my test just uses: # diskdevstat 5 60 which fails Version-Release number of selected component (if applicable): # rpm -qf /usr/share/systemtap/tapset/linux/vfs.stp systemtap-client-4.1-3.el8.x86_64 systemtap-devel-4.1-3.el8.x86_64 How reproducible: always Steps to Reproduce: 1. run diskdevstat 5 60 3. Actual results: semantic error: failed to retrieve location attribute for 'file' [man error::dwarf]: identifier '$file' at /usr/share/systemtap/tapset/linux/vfs.stp:1055:19 dieoffset: 0x36a4919 from /usr/lib/debug/lib/modules/4.18.0-107.el8.x86_64/vmlinux function: vfs_write at fs/read_write.c:546:3 inlined by vfs_write at fs/read_write.c:533:9 source: dev = __file_dev($file) ^ semantic error: unresolved type : identifier '$file' at :1055:19 source: dev = __file_dev($file) ^ Pass 2: analysis failed. [man error::pass2] Number of similar error messages suppressed: 6. Rerun with -v to see them. Expected results: no error? :) Additional info: