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.
Description of problem:
commit 8daeed9570af72eb135c8ded460d2888f05b2e68
Author: Mickaël Salaün <mic>
Date: Sun May 11 22:54:58 2014 +0200
closures: Create temporary file with O_TMPFILE and O_CLOEXEC when available
https://github.com/atgreen/libffi/commit/8daeed9570af72eb135c8ded460d2888f05b2e68
In RHEL-7, we had the patch backported via bz1151568 into libffi-3.0.13. In RHEL-8 we appear to have libffi-3.1. Upstream, it got into 3.2 and above, so this way, we lost the patch.
The related testcase has failed recently, proving the same scenario with firewalld, so I think it is a regression.
Version-Release number of selected component (if applicable):
libffi-3.1-18.el8
How reproducible:
Not easily, it failed in CI, however, when testing manually with the same testcase, I can't reproduce the scenario, because it depends on firewalld which hasn't the file opened in my case. However, there should be a simpler reproducer possible.
Steps to Reproduce:
1. run the linked testcase
2.
3.
Actual results:
Expected results:
Additional info:
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://access.redhat.com/errata/RHBA-2019:3652
Description of problem: commit 8daeed9570af72eb135c8ded460d2888f05b2e68 Author: Mickaël Salaün <mic> Date: Sun May 11 22:54:58 2014 +0200 closures: Create temporary file with O_TMPFILE and O_CLOEXEC when available https://github.com/atgreen/libffi/commit/8daeed9570af72eb135c8ded460d2888f05b2e68 In RHEL-7, we had the patch backported via bz1151568 into libffi-3.0.13. In RHEL-8 we appear to have libffi-3.1. Upstream, it got into 3.2 and above, so this way, we lost the patch. The related testcase has failed recently, proving the same scenario with firewalld, so I think it is a regression. Version-Release number of selected component (if applicable): libffi-3.1-18.el8 How reproducible: Not easily, it failed in CI, however, when testing manually with the same testcase, I can't reproduce the scenario, because it depends on firewalld which hasn't the file opened in my case. However, there should be a simpler reproducer possible. Steps to Reproduce: 1. run the linked testcase 2. 3. Actual results: Expected results: Additional info: