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.

Bug 2145242

Summary: a little problem in label probe wildcard expansion
Product: Red Hat Enterprise Linux 9 Reporter: Martin Cermak <mcermak>
Component: systemtapAssignee: Ryan Goldberg <rgoldber>
systemtap sub component: system-version QA Contact: Martin Cermak <mcermak>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: fche, lberk, mcermak, mjw, wcohen
Version: 9.2Keywords: Regression, Triaged
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemtap-4.8-2.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 07:37:36 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:

Description Martin Cermak 2022-11-23 15:21:06 UTC
systemtap-4.8-1.el9 doesn't correctly expand wildcards in label probes.  Problem description taken from PR29676:

Commit d922f3166 seems to have an unwanted side-effect related to labels.  The upstream testsuite has testcase labels.exp that started to fail with it.  From the user perspective the problem is that now stap -l (or -L) can return something like this:

process("/somedir/labels.x").function("_start").label("*")
process("/somedir/labels.x").function("deregister_tm_clones").label("*")
process("/somedir/labels.x").function("foo@/somedir/labels.c:5").label("init_an_int")

Note the label("*") in the above output. The star is a wildcard which should have been expanded, not printed out. Also the function pnlabel() can now start returning star, while, again, this is a wildcard that should have been expanded instead of returned.

Comment 1 William Cohen 2022-11-23 21:21:25 UTC
Rolled back to git commit a50bb747070b4bd592f3c32d5e83e4b508c6d8d7 (commit just before the change to wild card change).  See

$ sudo make installcheck RUNTESTFLAGS="--debug systemtap.base/labels.exp"
....
		=== systemtap Summary ===

# of expected passes		9
# of unexpected failures	1


For git commit 92e8ecb3329820992756bbbd3decd3d2ef4f490a see:

$ sudo make installcheck RUNTESTFLAGS="--debug systemtap.base/labels.exp"
....
		=== systemtap Summary ===

# of expected passes		7
# of unexpected failures	3

Comment 2 Martin Cermak 2023-01-16 09:20:54 UTC
labels.exp

Comment 5 errata-xmlrpc 2023-05-09 07:37:36 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/RHBA-2023:2241