Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-71581

glibc: Handle L3 cache sizes larger than 4 GiB on x86-64 [rhel-10]

XMLWordPrintable

    • No
    • Low
    • ZStream, Patch
    • 61c3450db96dce96ad2b24b4f0b548e6a46d68e5
    • rhel-sst-pt-libraries
    • ssg_platform_tools
    • None
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Approved Blocker
    • None
    • None
    • Unspecified Release Note Type - Unknown
    • x86_64
    • None

      There is an integer truncation issue in the glibc cache size computation. Values that are multiples of 4 GiB are reported as zero. This upstream commit fixes that:

      commit 61c3450db96dce96ad2b24b4f0b548e6a46d68e5
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Dec 17 18:12:03 2024 +0100

    x86: Avoid integer truncation with large cache sizes (bug 32470)
    
    Some hypervisors report 1 TiB L3 cache size.  This results
    in some variables incorrectly getting zeroed, causing crashes
    in memcpy/memmove because invariants are violated.

      I expect the only way to reproduce this issue today is with hypervisors that reported an incorrect L3 cache size. We do not readily have access to those, so we can only check that the patch is applied correctly.

              glibc-bugzilla Platform Tools - Libraries Bot
              fweimer@redhat.com Florian Weimer
              Platform Tools - Libraries Bot Platform Tools - Libraries Bot
              qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com qe-baseos-tools-bugs@redhat.com
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: