[Bug 2011421] Update Released

[Steve Langasek]

The verification of the Stable Release Update for glibc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2011421

Title:
  TDX azure instances crash during boot because of glibc bug

Status in glibc package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in glibc source package in Jammy:
  Fix Released
Status in linux-azure source package in Jammy:
  Invalid
Status in glibc source package in Kinetic:
  Won't Fix
Status in linux-azure source package in Kinetic:
  Won't Fix
Status in glibc source package in Lunar:
  Fix Released
Status in linux-azure source package in Lunar:
  New

Bug description:
  [IMPACT]

  Glibc in jammy and kinetic is affected by the following bug :
  https://sourceware.org/bugzilla/show_bug.cgi?id=29953

  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.

  The issue was reported because jammy tdx instances are failing to boot
  (crashing) on azure. The bug has been resolved upstream in
  https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b

  [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]

  Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953
  Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037

  In jammy we need 2 commits :
  https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321
  https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b

  In kinetic we just need :
  https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+subscriptions