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 2038794 - Backport futex_waitv() from Linux 5.16
Summary: Backport futex_waitv() from Linux 5.16
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.1
Assignee: Joel Savitz
QA Contact: Chunyu Hu
URL:
Whiteboard:
Depends On:
Blocks: 2086946
TreeView+ depends on / blocked
 
Reported: 2022-01-10 06:33 UTC by Neal Gompa
Modified: 2022-11-15 12:13 UTC (History)
9 users (show)

Fixed In Version: kernel-5.14.0-77.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2086946 (view as bug list)
Environment:
Last Closed: 2022-11-15 10:52:35 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/src/kernel centos-stream-9 merge_requests 578 0 None None None 2022-03-11 12:10:12 UTC
Red Hat Issue Tracker RHELPLAN-107218 0 None None None 2022-01-10 06:35:55 UTC
Red Hat Product Errata RHSA-2022:8267 0 None None None 2022-11-15 10:52:48 UTC

Description Neal Gompa 2022-01-10 06:33:12 UTC
Description of problem:
Linux 5.16 introduces the new futex_waitv(2) syscall, which allows to wait on multiple futexes with a single system call. This syscall is designed to work similarly to Windows NT's WaitForMultipleObjects API, which helps improve performance for applications running in Wine on Linux.

Please consider backporting this, so that Wine and other applications can take advantage of this functionality in RHEL 9.

Version-Release number of selected component (if applicable):
5.14.0-39.el9

Comment 1 Waiman Long 2022-01-10 15:19:23 UTC
The current RHEL9/Centos-Stream9 code base is based mostly on v5.15 with some 5.16 code mixed in. There is no current plan to backport the futex_waitv(2) code for the RHEL9.0 release as it will complicate our RT kernel work. Will get it into the next RHEL9.1 release instead.

Comment 2 Neal Gompa 2022-01-10 17:28:07 UTC
That's fine with me. I just wanted to get this on the radar so we have a timeline for it.

Comment 12 errata-xmlrpc 2022-11-15 10:52:35 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 (Moderate: kernel security, 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/RHSA-2022:8267


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