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.
Created attachment 1189624[details]
bitmasklist-bug.py - reproducer
Description of problem:
parse_affinity() function reports wrong affinity if CPU number is larger than 31
Version-Release number of selected component (if applicable):
python-linux-procfs-0.4.6-3.el7
How reproducible:
When affinity is set for CPU 32 and higher.
Attached reproducer with several showcases
Steps to Reproduce:
run the attached script bitmasklist-bug.py which calls the bitmasklist function directly with examples of affinity
Actual results:
parse_affinity() reports wrong affinity when affinity is set for CPUs 32 and higher
Expected results:
parse_affinity() reports correct affinity regardless of CPU number
Additional info:
I believe this is caused by bitmasklist() splitting the input line into array instead of treating it as long hexbitmask, the attached fix.patch produces expected result
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-2016-2532.html
Created attachment 1189624 [details] bitmasklist-bug.py - reproducer Description of problem: parse_affinity() function reports wrong affinity if CPU number is larger than 31 Version-Release number of selected component (if applicable): python-linux-procfs-0.4.6-3.el7 How reproducible: When affinity is set for CPU 32 and higher. Attached reproducer with several showcases Steps to Reproduce: run the attached script bitmasklist-bug.py which calls the bitmasklist function directly with examples of affinity Actual results: parse_affinity() reports wrong affinity when affinity is set for CPUs 32 and higher Expected results: parse_affinity() reports correct affinity regardless of CPU number Additional info: I believe this is caused by bitmasklist() splitting the input line into array instead of treating it as long hexbitmask, the attached fix.patch produces expected result