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.

Description of problem:

Gregg Leventhal has found that `perf top -p $PID` does not work in RHEL-7.

Version-Release number of selected component (if applicable):
recent RHEL-7 perf, e.g. 3.10.0-1090.el7

How reproducible:
100%

Steps to Reproduce:
yes > /dev/null &
perf top -p $!

Actual results:

NOTHING

Expected results:

perf top works

Patch(es) committed on kernel-3.10.0-1101.el7

*** Bug 1757947 has been marked as a duplicate of this bug. ***

RHEL 7.8 is likely months away based on the cycle of previous releases.  Is there any change for a back-ported fix being released sooner than 7.8?  I'd like to get an estimated date so that I can find out if my employees are willing to wait for the upstream fix, or if I'll need to patch this in my environment.

I just wanted to follow up and see if I can possibly get an ETA for 7.8 or the possibility of a back-port resolving this issue before then please.

I ended up resolving this on my own for 7.7, so feel free to close (as far as I am concerned WRT to backporting to 7.7).

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://access.redhat.com/errata/RHSA-2020:1016