Bug 2014228
Summary: | libffi: Python scripts crash with ANOM_ABEND when SELinux is enabled | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Paulo Andrade <pandrade> | |
Component: | libffi | Assignee: | DJ Delorie <dj> | |
Status: | CLOSED ERRATA | QA Contact: | Lenka Špačková <lkuprova> | |
Severity: | medium | Docs Contact: | Jacob Taylor Valdez <jvaldez> | |
Priority: | medium | |||
Version: | 8.4 | CC: | codonell, dj, fweimer, jvaldez, mcermak | |
Target Milestone: | rc | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | libffi-3.1-24.el8 | Doc Type: | Bug Fix | |
Doc Text: |
.`libffi` can now probe for executable memory with SELinux enabled
By default, `libffi` does not probe for executable memory when SELinux is enabled. As a consequence, programs which use `libffi` closures and `fork()` without immediately executing some other processes terminate unexpectedly when SELinux is enabled. With this update, `libffi` looks for a `/etc/sysconfig/libffi-force-shared-memory-check-first` file and, if it exists, probes for executable memory regardless of if SELinux is enabled. As a result, programs using `libffi` can safely `fork()` without crashing with SELinux enabled.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2152228 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-16 09:10:24 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2152228 |
Description
Paulo Andrade
2021-10-14 16:23:47 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 (libffi 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-2023:3014 |