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.
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 (new packages: systemtap), 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/RHBA-2022:2514
This is probably just a low prio kernel porting business. Please, consider fixing: 9.0 Server x86_64 # cat readpages.stp probe nfs.aop.readpages { log(name); printf("dev=%d\n", dev); printf("ino=%d\n", ino); printf("nr_pages=%d\n", nr_pages); printf("file=%d\n", file); printf("rpages=%d\n", rpages); printf("rsize=%d\n", rsize); printf("argstr=%s\n", argstr); printf("size=%d\n", size); printf("units=%s\n", units); } probe nfs.aop.readpages.return { log(name); printf("retstr=%s\n", retstr); printf("size=%d\n", size); printf("units=%s\n", units); } 9.0 Server x86_64 # 9.0 Server x86_64 # 9.0 Server x86_64 # stap -P -vp4 readpages.stp Pass 1: parsed user script and 482 library scripts using 106992virt/87820res/12180shr/75484data kb, in 300usr/100sys/396real ms. semantic error: unable to find local 'filp', [man error::dwarf] dieoffset 0x1cf974 in nfs, near pc 0x231d5 in nfs_readpages fs/nfs/read.c (alternatives: $file, $ret, $desc, $inode, $mapping)): identifier '$filp' at /usr/share/systemtap/tapset/linux/nfs.stp:982:16 source: file = $filp ^ semantic error: unable to find local 'filp', [man error::dwarf] dieoffset 0x1cf974 in nfs, near pc 0x231d5 in nfs_readpages fs/nfs/read.c (alternatives: $file, $ret, $desc, $inode, $mapping)): identifier '$filp' at :982:16 source: file = $filp ^ Pass 2: analyzed script: 2 probes, 15 functions, 2 embeds, 0 globals using 294596virt/277656res/14256shr/263088data kb, in 3370usr/470sys/3893real ms. Pass 2: analysis failed. [man error::pass2] 9.0 Server x86_64 # 9.0 Server x86_64 # rpm -q systemtap; uname -r systemtap-4.5-2.el9.x86_64 5.13.0-0.rc4.33.el9.x86_64 9.0 Server x86_64 #