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.
Comment 1Petr Viktorin (pviktori)
2016-07-07 08:49:05 UTC
Since pthreading uses ctypes and monkeypatches the standard library, I don't think "no architecture-specific code in python-pthreading" is a good reason to automatically blame Python.
Can you prepare a minimal reproducer?
Comment 2Charalampos Stratakis
2016-10-11 13:53:01 UTC
No reproducer was posted so reassigning it to the component that it originates from.
Based on mock and koji scratch builds of the same SRPM, the tests pass in F27 but not in F26 or RHEL 7. Therefore this is most likely in either python or libffi.
Comment 6Petr Viktorin (pviktori)
2018-04-11 10:17:35 UTC
We still don't have a good reproducer, and initial attempts to investigate didn't yield much.
The original comment about "no architecture-specific code in python-pthreading" is misleading, since pthreading uses ctypes.
We'll get to it when we have some free cycles, but it's low priority. Let us know if we need to allocate more time to it.
Comment 7Petr Viktorin (pviktori)
2018-06-07 14:15:04 UTC
Ok, I got access to a RHEL7/AArch64 VM on Beaker.
"python-pthreading tests fail on aarch64 with the output below. As there is no architecture-specific code in python-pthreading, I believe the issue is in python itself."
Well, there *is* architecture-specific code in python-pthreading:
# These come from pthread.h (via bits/pthreadtypes.h)
# We prefer to be on a safe side and use sizes for 64 bit implementation
SIZEOF_MUTEX_T = 40
SIZEOF_COND_T = 48
SIZEOF_MUTEXATTR_T = 4
These sizes in bytes are hardcoded values of sizeof(pthread_mutex_t), sizeof(pthread_cond_t) and sizeof(pthread_mutexattr_t) and you know what? ... The sizes are platform specific :-)
The tests pass with the following change:
diff --git a/pthread.py b/pthread.py
index 50d1e9a..a61c0c2 100644
--- a/pthread.py
+++ b/pthread.py
@@ -37,7 +37,7 @@ LIBPTHREAD = "libpthread.so.0"
# These come from pthread.h (via bits/pthreadtypes.h)
# We prefer to be on a safe side and use sizes for 64 bit implementation
-SIZEOF_MUTEX_T = 40
+SIZEOF_MUTEX_T = 48
SIZEOF_COND_T = 48
SIZEOF_MUTEXATTR_T = 4
Notes:
* the latest python-pthreading version (0.1.3-3) has been released 4 years ago: https://pypi.org/project/pthreading/
* On PyPI, the homepage is set to http://git.fedorahosted.org/git/?p=pthreading.git which now redirects to https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement?p=pthreading.git
* Source of the RPM package: https://src.fedoraproject.org/rpms/python-pthreading/tree/master
Comment 22Sandro Bonazzola
2019-10-22 06:31:11 UTC
(In reply to Nir Soffer from comment #20)
> Sandro, what kind of info do you need?
Need a release including https://gerrit.ovirt.org/#/c/94974/ but since this is not going to be in 4.3 I think we can close this bug.
4.4 is not going to use python-pthreading on el8