Bug 1855264

Summary: Missing explicit @cast() operators across tapset
Product: Red Hat Enterprise Linux 8 Reporter: Martin Cermak <mcermak>
Component: systemtapAssignee: Frank Ch. Eigler <fche>
systemtap sub component: system-version QA Contact: qe-baseos-tools-bugs
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: medium CC: dsmith, fche, lberk, mcermak, mjw
Version: 8.3Keywords: Bugfix
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: systemtap-4.3-2.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1852021 Environment:
Last Closed: 2020-11-04 03:59:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1852021    
Bug Blocks:    

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