Bug 1720600 - libffi is missing patch handling flags for open_temp_exec_file_name()
Summary: libffi is missing patch handling flags for open_temp_exec_file_name()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libffi
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: DJ Delorie
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-14 10:32 UTC by Michael Petlan
Modified: 2023-07-18 14:30 UTC (History)
4 users (show)

Fixed In Version: libffi-3.1-20.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:35:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3652 0 None None None 2019-11-05 22:35:09 UTC

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


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