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.
Verified using systemtap.base/bz5274.exp. There is a small issue in the testcase though: Due to updates in blacklist stap now reports a warning to stderr:
=======
# stap systemtap.base/bz5274.stp -c ./systemtap.base/bz5274 > /dev/null
WARNING: function _start return probe is blacklisted: keyword at systemtap.base/bz5274.stp:5:1
source: probe process.function("*").return {
^
=======
This warning is being caught() and makes the testcase "untested". Hiding warnings using -w fixes the testcase for me.
Hmm, actually there is one more ppc64 specific thing that makes the testcase untested: Using 2.6.32-551.el6.ppc64 the testcase ends up on uretprobes_p check. Looking closer I suspect utrace_orig_p() in lib/systemtap.exp not to work well.
=======
# Test for kernel built-in utrace (CONFIG_UTRACE).
# Only original rhel5/6-era utrace need apply.
proc utrace_orig_p {} {
# We want utrace_attach (rhel5) or utrace_attach_task (rhel6), but don't
# get confused by the private module version of any active stap module.
return [grep_kallsyms "T utrace_attach"]
}
=======
On mentioned kernel we have:
=======
6.7 S ppc64 # cat /proc/kallsyms | grep "T utrace_attach"
6.7 S ppc64 #
6.7 S ppc64 # cat /proc/kallsyms | grep "utrace_attach"
c0000000001032a0 T .utrace_attach_task
c000000000103610 T .utrace_attach_pid
c000000000843508 d __ksymtab_utrace_attach_pid
c000000000843518 d __ksymtab_utrace_attach_task
c000000000850f60 d __kcrctab_utrace_attach_pid
c000000000850f68 d __kcrctab_utrace_attach_task
c000000000857ab7 r __kstrtab_utrace_attach_pid
c000000000857ac9 r __kstrtab_utrace_attach_task
c000000000f44830 D utrace_attach_task
c000000000f44840 D utrace_attach_pid
6.7 S ppc64 #
=======
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, 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://rhn.redhat.com/errata/RHBA-2015-1333.html