[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-aws - 6.2.0-1015.15 --- linux-aws (6.2.0-1015.15) lunar; urgency=medium * lunar/linux-aws: 6.2.0-1015.15 -proposed tracker (LP: #2038059) * SEV_SNP failure to init (LP: #2037316) - x86/sev-es: Allow copy_from_kernel_nofault in earlier boot - x86/sev-es: Only set x86_virt_bits to correct value [ Ubuntu: 6.2.0-36.37 ] * lunar/linux: 6.2.0-36.37 -proposed tracker (LP: #2038076) * Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7 (LP: #2035181) - selftests/bpf: fix static assert compilation issue for test_cls_*.c * CVE-2023-4244 - netfilter: nf_tables: don't skip expired elements during walk - netfilter: nf_tables: adapt set backend to use GC transaction API - netfilter: nft_set_hash: mark set element as dead when deleting from packet path - netfilter: nf_tables: GC transaction API to avoid race with control plane - netfilter: nf_tables: don't fail inserts if duplicate has expired - netfilter: nf_tables: fix kdoc warnings after gc rework - netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path - netfilter: nf_tables: GC transaction race with netns dismantle - netfilter: nf_tables: GC transaction race with abort path - netfilter: nf_tables: use correct lock to protect gc_list - netfilter: nf_tables: defer gc run if previous batch is still pending - netfilter: nft_dynset: disallow object maps - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-4563 - netfilter: nf_tables: remove busy mark and gc batch API * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4623 - net/sched: sch_hfsc: Ensure inner classes have fsc curve * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077) - ALSA: hda/realtek - ALC287 I2S speaker platform support * Lunar update: upstream stable patchset 2023-09-21 (LP: #2037005) - Upstream stable to v6.1.41, v6.4.6 - io_uring: treat -EAGAIN for REQ_F_NOWAIT as final for io-wq - ALSA: hda/realtek - remove 3k pull low procedure - ALSA: hda/realtek: Add quirk for Clevo NS70AU - ALSA: hda/realtek: Enable Mute LED on HP Laptop 15s-eq2xxx - maple_tree: set the node limit when creating a new root node - maple_tree: fix node allocation testing on 32 bit - keys: Fix linking a duplicate key to a keyring's assoc_array - perf probe: Add test for regression introduced by switch to die_get_decl_file() - btrfs: fix warning when putting transaction with qgroups enabled after abort - fuse: revalidate: don't invalidate if interrupted - fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT - btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand - btrfs: zoned: fix memory leak after finding block group with super blocks - fuse: ioctl: translate ENOSYS in outarg - btrfs: fix race between balance and cancel/pause - selftests: tc: set timeout to 15 minutes - selftests: tc: add 'ct' action kconfig dep - regmap: Drop initial version of maximum transfer length fixes - of: Preserve "of-display" device name for compatibility - regmap: Account for register length in SMBus I/O limits - arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes - can: mcp251xfd: __mcp251xfd_chip_set_mode(): increase poll timeout - can: bcm: Fix UAF in bcm_proc_show() - can: gs_usb: gs_can_open(): improve error handling - selftests: tc: add ConnTrack procfs kconfig - dma-buf/dma-resv: Stop leaking on krealloc() failure - drm/amdgpu/vkms: relax timer deactivation by hrtimer_try_to_cancel - drm/amdgpu/pm: make gfxclock consistent for sienna cichlid - drm/amdgpu/pm: make mclk consistent for smu 13.0.7 - drm/client: Fix memory leak in drm_client_target_cloned - drm/client: Fix memory leak in drm_client_modeset_probe - drm/amd/display: only accept async flips for fast updates - drm/amd/display: Disable MPC split by default on special asic - drm/amd/display: check TG is non-null before checking if enabled - drm/amd/display: Keep PHY active for DP displays on DCN31 - ASoC: fsl_sai: Disable bit clock with transmitter - ASoC: fsl_sai: Revert "ASoC: fsl_sai: Enable MCTL_MCLK_EN bit for master mode" - ASoC: tegra: Fix ADX byte map - ASoC: rt5640: Fix sleep in atomic context - ASoC: cs42l51: fix driver to properly autoload with automatic module loading - ASoC: codecs: wcd938x: fix missing clsh ctrl error handling - ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove - ASoC: qdsp6: audioreach: fix topology probe deferral - ASoC: tegra: Fix AMX byte map - ASoC: codecs: wcd938x: fix resource leaks on component remove - ASoC: codecs: wcd938x: fix missing mbhc init error handling - ASoC:
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug is awaiting verification that the linux- aws-6.5/6.5.0-1008.8~22.04.1 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-jammy-linux- aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'. 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 added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-gcp - 6.2.0-1017.19 --- linux-gcp (6.2.0-1017.19) lunar; urgency=medium * lunar/linux-gcp: 6.2.0-1017.19 -proposed tracker (LP: #2038064) * CVE-2023-42755 - [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6 * SEV_SNP failure to init (LP: #2037316) - x86/sev-es: Allow copy_from_kernel_nofault in earlier boot - x86/sev-es: Only set x86_virt_bits to correct value [ Ubuntu: 6.2.0-35.35 ] * lunar/linux: 6.2.0-35.35 -proposed tracker (LP: #2038229) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2023-4244 - netfilter: nf_tables: don't skip expired elements during walk - netfilter: nf_tables: integrate pipapo into commit protocol - netfilter: nft_set_rbtree: fix overlap expiration walk - netfilter: nf_tables: adapt set backend to use GC transaction API - netfilter: nft_set_hash: mark set element as dead when deleting from packet path - netfilter: nf_tables: drop map element references from preparation phase - netfilter: nf_tables: GC transaction API to avoid race with control plane - netfilter: nf_tables: remove busy mark and gc batch API - netfilter: nf_tables: don't fail inserts if duplicate has expired - netfilter: nf_tables: fix kdoc warnings after gc rework - netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path - netfilter: nf_tables: GC transaction race with netns dismantle - netfilter: nf_tables: GC transaction race with abort path - netfilter: nf_tables: use correct lock to protect gc_list - netfilter: nf_tables: defer gc run if previous batch is still pending - netfilter: nft_dynset: disallow object maps - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5197 - netfilter: nf_tables: skip bound chain in netns release path - netfilter: nf_tables: disallow rule removal from chain binding * CVE-2023-4921 - net: sched: sch_qfq: Fix UAF in qfq_dequeue() * CVE-2023-4881 - netfilter: nftables: exthdr: fix 4-byte stack OOB write * CVE-2023-4623 - net/sched: sch_hfsc: Ensure inner classes have fsc curve * CVE-2023-4622 - af_unix: Fix null-ptr-deref in unix_stream_sendpage(). * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-42755 - net/sched: Retire rsvp classifier - [Config] remove NET_CLS_RSVP and NET_CLS_RSVP6 * CVE-2023-42753 - netfilter: ipset: add the missing IP_SET_HASH_WITH_NET0 macro for ip_set_hash_netportnet.c * CVE-2023-42752 - igmp: limit igmpv3_newpack() packet size to IP_MAX_MTU - net: add SKB_HEAD_ALIGN() helper - net: remove osize variable in __alloc_skb() - net: factorize code in kmalloc_reserve() - net: deal with integer overflows in kmalloc_reserve() * CVE-2023-34319 - xen/netback: Fix buffer overrun triggered by unusual packet -- John Cabaj Thu, 05 Oct 2023 21:59:43 -0500 ** Changed in: linux-gcp (Ubuntu Lunar) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-34319 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42752 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42753 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42755 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-42756 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4622 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4623 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4881 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4921 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5197 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
Tested the kernel from lunar proposed (6.2.0-1018-gcp) on GCP n2d instances. The image boots with sev enabled: john_cabaj@john-cabaj-sev-snp2:~$ sudo dmesg | grep -i sev [0.303257] Memory Encryption Features active: AMD SEV ** Tags removed: verification-needed-lunar-linux-gcp ** Tags added: verification-done-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
** Changed in: linux-aws (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Mantic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
I did test the kernel from lunar proposed (6.2.0.1015.16) on AWS. The image boots with sev-snp enabled: # sudo dmesg | grep -i sev [5.563677] Memory Encryption Features active: AMD SEV SEV-ES SEV-SNP [6.140250] SEV: Using SNP CPUID table, 64 entries present. [8.507286] SEV: SNP guest platform device initialized. [ 20.829729] sev-guest sev-guest: Initialized SEV guest driver (using vmpck_id 0) # apt-cache policy linux-aws linux-aws: Installed: 6.2.0.1015.16 Candidate: 6.2.0.1015.16 Version table: *** 6.2.0.1015.16 100 100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages 100 /var/lib/dpkg/status 6.2.0.1013.14 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 6.2.0.1003.4 500 500 http://us-east-2.ec2.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ** Tags removed: verification-needed-lunar-linux-aws ** Tags added: verification-done-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
This bug is awaiting verification that the linux-aws/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-aws' to 'verification-done-lunar- linux-aws'. If the problem still exists, change the tag 'verification- needed-lunar-linux-aws' to 'verification-failed-lunar-linux-aws'. 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 added: kernel-spammed-lunar-linux-aws-v2 verification-needed-lunar-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
This bug is awaiting verification that the linux-gcp/6.2.0-1017.19 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-gcp' to 'verification-done-lunar- linux-gcp'. If the problem still exists, change the tag 'verification- needed-lunar-linux-gcp' to 'verification-failed-lunar-linux-gcp'. 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 added: kernel-spammed-lunar-linux-gcp-v2 verification-needed-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-gcp - 6.5.0-1006.6
---
linux-gcp (6.5.0-1006.6) mantic; urgency=medium
* mantic/linux-gcp: 6.5.0-1006.6 -proposed tracker (LP: #2037626)
* SEV_SNP failure to init (LP: #2037316)
- x86/sev-es: Allow copy_from_kernel_nofault in earlier boot
- x86/sev-es: Only set x86_virt_bits to correct value
* Miscellaneous Ubuntu changes
- [Config] update gcc version in annotations
[ Ubuntu: 6.5.0-7.7 ]
* mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611)
* kexec enable to load/kdump zstd compressed zimg (LP: #2037398)
- [Packaging] Revert arm64 image format to Image.gz
* Mantic minimized/minimal cloud images do not receive IP address during
provisioning (LP: #2036968)
- [Config] Enable virtio-net as built-in to avoid race
* Miscellaneous Ubuntu changes
- SAUCE: Add mdev_set_iommu_device() kABI
- [Config] update gcc version in annotations
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Define a local bpf_perf_link to fix accessing its fields
- bpftool: Use a local copy of BPF_LINK_TYPE_PERF_EVENT in pid_iter.bpf.c
- bpftool: Use a local bpf_perf_event_value to fix accessing its fields
- libbpf: Fix realloc API handling in zero-sized
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-aws - 6.5.0-1007.7
---
linux-aws (6.5.0-1007.7) mantic; urgency=medium
* mantic/linux-aws: 6.5.0-1007.7 -proposed tracker (LP: #2037624)
* SEV_SNP failure to init (LP: #2037316)
- x86/sev-es: Allow copy_from_kernel_nofault in earlier boot
- x86/sev-es: Only set x86_virt_bits to correct value
* Miscellaneous Ubuntu changes
- [Config] update toolchain version in annotations
[ Ubuntu: 6.5.0-7.7 ]
* mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611)
* kexec enable to load/kdump zstd compressed zimg (LP: #2037398)
- [Packaging] Revert arm64 image format to Image.gz
* Mantic minimized/minimal cloud images do not receive IP address during
provisioning (LP: #2036968)
- [Config] Enable virtio-net as built-in to avoid race
* Miscellaneous Ubuntu changes
- SAUCE: Add mdev_set_iommu_device() kABI
- [Config] update gcc version in annotations
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Define a local bpf_perf_link to fix accessing its fields
- bpftool: Use a local copy of BPF_LINK_TYPE_PERF_EVENT in pid_iter.bpf.c
- bpftool: Use a local bpf_perf_event_value to fix accessing its fields
- libbpf: Fix realloc API handling in
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2037316] Re: SEV_SNP failure to init
Patches submitted to mantic:linux-gcp and lunar:linux-gcp for 2023.10.02 SRU cycle. jammy:linux-gcp-6.2 will get changes from lunar:linux-gcp during aforementioned SRU cycle. ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2037316/+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
