[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug is awaiting verification that the linux-azure/6.2.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar- linux-azure'. If the problem still exists, change the tag 'verification- needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done ** Tags added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-fde-6.2 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 linux-azure-fde-6.2 package in Ubuntu: New Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in linux-azure-fde-6.2 source package in Jammy: Fix Released Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in linux-azure-fde-6.2 source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: Fix Released Status in linux-azure-fde-6.2 source package in Lunar: Fix Released 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug was fixed in the package linux-azure-fde-6.2 - 6.2.0-1014.14~22.04.1.1 --- linux-azure-fde-6.2 (6.2.0-1014.14~22.04.1.1) jammy; urgency=medium * jammy/linux-azure-fde-6.2: 6.2.0-1014.14~22.04.1.1 -proposed tracker (LP: #2035364) * TDX azure instances crash during boot because of glibc bug (LP: #2011421) - [Packaging] Use latest glibc from ubuntu-core-initramfs linux-azure-fde-6.2 (6.2.0-1013.13~22.04.1.1) jammy; urgency=medium * Master version: 6.2.0-1013.13~22.04.1 * jammy/linux-azure-fde-6.2: 6.2.0-1013.13~22.04.1.1 -proposed tracker (LP: #2033764) linux-azure-fde-6.2 (6.2.0-1012.12~22.04.1.1) jammy; urgency=medium * jammy/linux-azure-fde-6.2: 6.2.0-1012.12~22.04.1.1 -proposed tracker (LP: #2034142) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts linux-azure-fde-6.2 (6.2.0-1011.11~22.04.1.1) jammy; urgency=medium * Master version: 6.2.0-1011.11~22.04.1 * jammy/linux-azure-fde-6.2: 6.2.0-1011.11~22.04.1.1 -proposed tracker (LP: #2030366) linux-azure-fde-6.2 (6.2.0-1010.10~22.04.1.1) jammy; urgency=medium * jammy/linux-azure-fde-6.2: 6.2.0-1010.10~22.04.1.1 -proposed tracker (LP: #2030532) linux-azure-fde-6.2 (6.2.0-1009.9~22.04.3.1) jammy; urgency=medium * jammy/linux-azure-fde-6.2: 6.2.0-1009.9~22.04.3.1 -proposed tracker (LP: #2029293) * Packaging resync (LP: #1786013) - [Packaging] update variants linux-azure-fde-6.2 (6.2.0-1009.9~22.04.2.1) jammy; urgency=medium * Master version: 6.2.0-1009.9~22.04.2 * jammy/linux-azure-fde-6.2: 6.2.0-1009.9~22.04.2.1 -proposed tracker (LP: #2026474) * Miscellaneous Ubuntu changes - generate-depends: do not silently ignore failures linux-azure-fde-6.2 (6.2.0-1009.9~22.04.1.1) jammy; urgency=medium * Master version: 6.2.0-1009.9~22.04.1 * jammy/linux-azure-fde-6.2: 6.2.0-1009.9~22.04.1.1 -proposed tracker (LP: #2026474) linux-azure-fde-6.2 (6.2.0-1008.8~22.04.1.1) jammy; urgency=medium * jammy/linux-azure-fde-6.2: 6.2.0-1008.8~22.04.1.1 -proposed tracker (LP: #2026739) linux-azure-fde-6.2 (6.2.0-1007.7~22.04.1.1) jammy; urgency=medium * Master version: 6.2.0-1007.7~22.04.1 * jammy/linux-azure-fde-6.2: 6.2.0-1007.7~22.04.1.1 -proposed tracker (LP: #2024532) -- Tim Gardner Thu, 14 Sep 2023 12:25:12 -0600 ** Changed in: linux-azure-fde-6.2 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu Lunar) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-40982 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1206 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1380 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20569 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20588 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20593 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2124 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-21264 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2176 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2612 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2640 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2898 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-30456 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31084 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31248 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3141 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31436 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3212 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32233 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32629 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3269 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3390 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-35001 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3609 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3610 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3611 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3776 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3777 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3995 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4004 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4015 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-40283 **
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Also affects: linux-azure-fde-6.2 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-fde-6.2 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure-fde-6.2 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-azure-fde-6.2 (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-fde-6.2 (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: linux-azure-fde-6.2 (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-fde-6.2 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 linux-azure-fde-6.2 package in Ubuntu: New Status in glibc source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Invalid Status in linux-azure-fde-6.2 source package in Jammy: Fix Committed Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: Won't Fix Status in linux-azure-fde-6.2 source package in Kinetic: Won't Fix Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure-fde-6.2 source package in Lunar: Fix Released 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
The glibc workaround has been removed from the kernel. This patch only affected users of TDX in CVM images on an Azure paravisor with HCL. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: Fix Committed 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: Fix Committed 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug was fixed in the package glibc - 2.35-0ubuntu3.3 --- glibc (2.35-0ubuntu3.3) jammy; urgency=medium * Drop SVE patches due to kernal-related performance regression * Fix the armhf stripping exception for ld.so (LP: #1927192) glibc (2.35-0ubuntu3.2) jammy; urgency=medium * d/rules.d/debhelper.mk: fix permissions of libc.so (LP: #1989082) * Cherry-picks from upstream: - d/p/lp1999551/*: arm64 memcpy optimization (LP: #1999551) - d/p/lp1995362*.patch: Fix ldd segfault with missing libs (LP: #1995362) - d/p/lp2007796*: Fix missing cancellation point in pthread (LP: #2007796) - d/p/lp2007599*: add new tunables for s390x (LP: #2007599) - d/p/lp2011421/*: Fix crash on TDX-enabled platforms (LP: #2011421) - d/p/lp1992159*: Fix socket.h headers for non-GNU compilers (LP: #1992159) -- Simon Chopin Wed, 26 Jul 2023 10:27:54 +0200 ** Changed in: glibc (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
Sorry, there were some potential regressions that needed investigating, and we're still waiting on a few benchmark results for bug 1999551. Other than that the overall autopkgtest results are in good shape, so assuming the benchmarks show what we want them to, this shouldn't be long. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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 Committed 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
@schopin, Do you have any ETA of when this will be released ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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 Committed 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Changed in: glibc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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 Committed 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
# VERIFICATION JAMMY - glibc On an Azure TDX instance installed libc6 and libc-bin from -proposed and rebooted. It boots successfully. I also installed a test kernel with the kernel workaround reverted and it also boots with no problems. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Committed 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
Hello Ioanna, or anyone else affected, Accepted glibc into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.35-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glibc (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Committed 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Changed in: glibc (Ubuntu Jammy) Status: Incomplete => In Progress ** Also affects: glibc (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: In Progress 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
Sorry, my bad for the status, we discussed this offline with joalif. I'm not planning on fixing this in Kinetic as the affected platform is more of an LTS user, as I understand, and the kinetic EOL is approaching. Given the time it can take for a glibc SRU to go through -proposed even when there's nothing breaking, I don't think it worth the trouble. I might be wrong, though :) ** Changed in: glibc (Ubuntu Kinetic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Incomplete 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: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
This bug is marked as 'in progress' for glibc in both jammy and kinetic, but there is no glibc SRU in the kinetic queue. As the normal SRU process is to fix bugs in later releases before earlier releases, there needs to be some clarification about the plan here. This is also the only one of the several bugs referenced in this jammy SRU that has a kinetic or lunar task; all the others have only the main task closed as fix released. So it would be helpful to clarify (perhaps by opening and then cosing additional per-series tasks) exactly when the bug was fixed post-jammy. ** Changed in: glibc (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Incomplete Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: In Progress Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
The kernel patch is only for Kinetic linux-azure (5.19). The Jammy backport (linux-azure-5.19) will get it automatically. ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: New Status in glibc source package in Jammy: In Progress Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
The kernel patch won't be released in an SRU until after the glibc fix has been released to updates. Otherwise there will be a window where TDX support is regressed. ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: glibc (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: glibc (Ubuntu Jammy) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Changed in: glibc (Ubuntu Kinetic) Status: Triaged => In Progress ** Changed in: glibc (Ubuntu Kinetic) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure 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: New Status in linux-azure package in Ubuntu: New Status in glibc source package in Jammy: In Progress Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: In Progress Status in linux-azure source package in Kinetic: In Progress 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
