When cpuid reports no information on a shared cache, the
x86_non_temporal_threshold will be set to zero, causing memcpy/memset to
behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates
that the minimum value must be 0x4040, but this is not enforced for the
default value.
[IMPACT]
Glibc in jammy and kinetic is affected by the following bug : /sourceware. org/bugzilla/ show_bug. cgi?id= 29953
https:/
When cpuid reports no information on a shared cache, the temporal_ threshold will be set to zero, causing memcpy/memset to x86/dl- cacheinfo. h indicates
x86_non_
behave wrong for mid-sized operations. sysdeps/
that the minimum value must be 0x4040, but this is not enforced for the
default value.
The issue was reported because jammy tdx instances are failing to boot /sourceware. org/git/ gitweb. cgi?p=glibc. git;h=48b74865c 63840b288bd85b4 d8743533b73b339 b
(crashing) on azure. The bug has been resolved upstream in
https:/
[TEST CASE]
Test case requires an azure tdx instance.
Microsoft has tested a test package with the above commit and
confirmed that instances boot successfully.
[REGRESSION POTENTIAL]
The patches have been accepted upstream. They modify code for x86 architecture, so any
potential regression would affect x86.
[OTHER]
In jammy we need 2 commits : /sourceware. org/git/ gitweb. cgi?p=glibc. git;h=b446822b6 ae4e8149902a78c dd4a886634ad632 1 /sourceware. org/git/ gitweb. cgi?p=glibc. git;h=48b74865c 63840b288bd85b4 d8743533b73b339 b
https:/
https:/
In kinetic we just need : /sourceware. org/git/ gitweb. cgi?p=glibc. git;h=48b74865c 63840b288bd85b4 d8743533b73b339 b
https:/