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 1181624 - multiprocessing BaseManager serve_client() does not check EINTR on recv
Summary: multiprocessing BaseManager serve_client() does not check EINTR on recv
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python
Version: 7.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Robert Kuska
QA Contact: Branislav Náter
URL:
Whiteboard:
Depends On:
Blocks: 841486 1180864 1210347
TreeView+ depends on / blocked
 
Reported: 2015-01-13 13:41 UTC by Dan Kenigsberg
Modified: 2016-04-18 10:17 UTC (History)
9 users (show)

Fixed In Version: python-2.7.5-19.el7
Doc Type: Bug Fix
Doc Text:
Previously, the BaseManager class terminated unexpectedly when multiple signals were received on the same process. With this update, the multiprocessing module has been modified so that its methods ignore the "interrupted function" (EINTR) error, and the described crash no longer occurs.
Clone Of: 1180864
: 1210347 (view as bug list)
Environment:
Last Closed: 2015-11-19 12:43:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Python 17097 0 None None None Never
Red Hat Product Errata RHSA-2015:2101 0 normal SHIPPED_LIVE Moderate: python security, bug fix, and enhancement update 2015-11-19 11:04:15 UTC

Description Dan Kenigsberg 2015-01-13 13:41:30 UTC
+++ This bug was initially created as a clone of Bug #1180864 +++

Description of problem:
There is a problem with using BaseManager and receiving signals on the same process, there was a bug opened on python [1] and it was fixed for 2.7 and 3.x.
We asked to backport this to el6, but now realized that it's not even in el7. can this be backported to python2.7.5?

[1] - http://bugs.python.org/issue17097

Version-Release number of selected component (if applicable):
python-2.7.5-16.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Included in the python bug [1]

Comment 1 Bohuslav "Slavek" Kabrda 2015-01-13 14:06:11 UTC
We can fix this for 7.2 using upstream patch [1] linked to the referenced upstream issue.

[1] https://hg.python.org/cpython/rev/bc34fe4a0d58

Comment 9 errata-xmlrpc 2015-11-19 12:43:10 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, 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/RHSA-2015-2101.html


Note You need to log in before you can comment on or make changes to this bug.