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.
Cause
- selinux library was linked to ps in run time and wasn't correctly closed
- extended format in pmap was using incorrectly declared variables
Consequence
- memory leak occurs when showing selinux flags
- pmap could have unexpected behaviour
Fix
- selinux library is now linked to ps in build time
- variables are nullified and declared in correct place
Result
- memory leak doesn't occur now
- pmap doesn't rely on random circumstances
Created attachment 488713[details]
Proposed changed procps-3.2.8-pmap-smaps.patch
Changed procps-3.2.8-pmap-smaps.patch. Variables are nullified and moved to right position.
Yes, that is right. Initialization of 'start' is outside the loop because it is used in next iterations. 'end' is used only in the same iteration as sscanf.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause
- selinux library was linked to ps in run time and wasn't correctly closed
- extended format in pmap was using incorrectly declared variables
Consequence
- memory leak occurs when showing selinux flags
- pmap could have unexpected behaviour
Fix
- selinux library is now linked to ps in build time
- variables are nullified and declared in correct place
Result
- memory leak doesn't occur now
- pmap doesn't rely on random circumstances
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.
http://rhn.redhat.com/errata/RHBA-2011-1554.html
Created attachment 488713 [details] Proposed changed procps-3.2.8-pmap-smaps.patch Changed procps-3.2.8-pmap-smaps.patch. Variables are nullified and moved to right position.