Bug 1720600

Summary: libffi is missing patch handling flags for open_temp_exec_file_name()
Product: Red Hat Enterprise Linux 8 Reporter: Michael Petlan <mpetlan>
Component: libffiAssignee: DJ Delorie <dj>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: codonell, fweimer, mcermak, mnewsome
Target Milestone: rcKeywords: Patch, Regression
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libffi-3.1-20.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:35:09 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:

Description Michael Petlan 2019-06-14 10:32:26 UTC
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:

Comment 6 errata-xmlrpc 2019-11-05 22:35:09 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://access.redhat.com/errata/RHBA-2019:3652