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.

+++ This bug was initially created as a clone of Bug #2184728 +++

Dear Red Hat team,

we would like to ask wether you could backport the following commit 

https://github.com/util-linux/util-linux/commit/2fa4168c8bc9d5438bc1dfadda293c7c21b6fa59

to the supported RHEL 8/9 versions.
                                                                                                                                                              

Thank you
Michael

--- Additional comment from Michael Trapp on 2023-04-24 09:23:29 UTC ---

Increased severity because, this patch helps to prevent a possible performance degradation of libuuid. Depending on the workflow, uuid consumption is a critical part of a SAP system.

--- Additional comment from Michal Hlavinka on 2023-04-26 07:37:11 UTC ---

reassigning to correct component

--- Additional comment from Karel Zak on 2023-04-26 14:32:42 UTC ---

The cache-related changes are relatively small, so from my point of view, it's possible to backport from the current upstream to RHEL (probably by "git diff HEAD upstream --  libuuid/src/gen_uuid.c" as there are more changes than in the commit 2fa4168c8bc9d5438bc1dfadda293c7c21b6fa59).

Can you please provide the version info of the fixed libuuid rmps.

(In reply to Michael Trapp from comment #2)
> Can you please provide the version info of the fixed libuuid rmps.

The bugfix has not been released yet; it's planned for RHEL 9.3.

@michael.trapp please, can test RHEL-9 backport of the libuuidd cache in your environment? Thanks!

The rhel-9 packages are available at: https://people.redhat.com/kzak/bz2189947/x86_64

tested libuuid-2.37.4-13.el9.x86_64.rpm + uuidd-2.37.4-13.el9.x86_64.rpm on RHEL 9.2

Thanks for the backport!

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 (util-linux 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:6706