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.
Bug 1855264 - Missing explicit @cast() operators across tapset
Summary: Missing explicit @cast() operators across tapset
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemtap
Version: 8.3
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Frank Ch. Eigler
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1852021
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-09 11:59 UTC by Martin Cermak
Modified: 2021-09-17 14:55 UTC (History)
5 users (show)

Fixed In Version: systemtap-4.3-2.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 1852021
Environment:
Last Closed: 2020-11-04 03:59:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Cermak 2020-07-09 11:59:49 UTC 
+++ This bug was initially created as a clone of Bug #1852021 +++

Upstream Commit 00ee19ff030f665df7e087a579f39105256a0253 changed how @cast()
operations work and they no longer default to using the kernel
debuginfo for type information.  Need to include kernel as location for
this information for the  @cast() rather than just assuming a default.

There is a series of related patches upstream addressing this, at least some of which (if not all) probably need backporting to RHEL:

$ git log --all --grep='Commit 00ee19ff030f665df7e087a579f39105256a0253 changed how @cast' --oneline
403e92779 (HEAD -> master, origin/master, origin/HEAD) PR26181: Use explicit @cast() within get_ip_from_client()
a948c291c Use explicit @cast() operators pointing to kernel for tapsets
822ed2692 (origin/wcohen/tapset_cast) Use explicit @cast() operators pointing to kernel for tapsets
3d922919d Use explicit @cast() operators for periodic.stp
9eb37102d Use explicit @cast() operators for pfiles.stp and ioctl_handler.stp
717b7dddd Use explicit @cast() operators to fslatency-nd.stp and fsslower-nd.stp
2b2b6a622 Fix sizeof.stp to explicitly use kernel debuginfo if one not specified
$ 

Not having them backported breaks at least some NFS related test scenarios covered with a qe test case:

/tools/systemtap/Regression/semantic-error-nfs-proc-read_setup
/tools/systemtap/Regression/nfsd-open-status-semantic-error
Comment 7 errata-xmlrpc 2020-11-04 03:59:08 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemtap bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4801
Note You need to log in before you can comment on or make changes to this bug.