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 2105814 - [s390x] memstrack does not tracking memory allocation details related to modules.
Summary: [s390x] memstrack does not tracking memory allocation details related to modu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: memstrack
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: ltao
QA Contact: Li Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-10 18:21 UTC by rcheerla
Modified: 2022-11-15 11:43 UTC (History)
2 users (show)

Fixed In Version: memstrack-0.2.4-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:35:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-127363 0 None None None 2022-07-10 18:23:38 UTC
Red Hat Product Errata RHBA-2022:8199 0 None None None 2022-11-15 10:35:59 UTC

Description rcheerla 2022-07-10 18:21:21 UTC 
Description of problem: On s389x arch, memstrack tool failed to track the memory allocation details of modules. 


Version-Release number of selected component (if applicable):

Kernel version : 5.14.0-125.kpq0.el9.s390x
memstrack      : memstrack-0.2.3-2.el9.s390x


How reproducible: Always.


Steps to Reproduce:

1. Run below command on rhel9 s390x system.
   $ memstrack --notui --report module_summary,module_top,task_top --output report_result.txt
   $ modprobe ext4   <-- run it from another terminal 

Actual results:

cat report_result.txt
~~~~~~~~~~~~~~~~~~~~~~~~~~

======== Report format module_summary: ========
Module  using 0.0MB (0 pages), peak allocation 0.0MB (0 pages)
Module vfio_iommu_type1 using 0.0MB (0 pages), peak allocation 0.0MB (0 pages)
Module xfs using 0.0MB (0 pages), peak allocation 0.0MB (0 pages)
======== Report format module_summary END ========

======== Report format module_top: ========
Top stack usage of module :
  (null) Pages: 0 (peak: 0)
Top stack usage of module vfio_iommu_type1:
  (null) Pages: 0 (peak: 0)
Top stack usage of module xfs:
  (null) Pages: 0 (peak: 0)
======== Report format module_top END ========

======== Report format task_top: ========
======== Report format task_top END ========

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expected results:

It should track and display the stack information. 

Additional info: It is working find in x86_64 and ppc64le arch.
Comment 8 errata-xmlrpc 2022-11-15 10:35:57 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 (memstrack 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-2022:8199
Note You need to log in before you can comment on or make changes to this bug.