[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
** No longer affects: linux-gke (Ubuntu Focal) ** No longer affects: linux-gke (Ubuntu Mantic) ** No longer affects: linux-gke (Ubuntu Lunar) -- 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: Invalid Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gke source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
Thanks @mloza1 - I see well this looks different from the issue I am investigating, but maybe I can still help. There are 10s of thousands of changes between linux-image-5.15.0-25 and linux-image-5.15.0-67 so it's difficult to know what caused this. I think bisecting the changes is our best bet. Maybe you can try to narrow down which Ubuntu kernel started to fail this use-case? If you can find out which kernel version exactly started to fail that would be helpful. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM hangs No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 I'm able to reproduce the issue using the following kernels: linux-image-5.15.0-67-generic_5.15.0-67.74_amd64.deb linux-image-5.15.0-68-generic_5.15.0-68.75_amd64.deb linux-image-5.15.0-69-generic_5.15.0-69.76_amd64.deb linux-image-5.15.0-70-generic_5.15.0-70.77_amd64.deb linux-image-5.15.0-72-generic_5.15.0-72.79_amd64.deb linux-image-5.15.0-73-generic_5.15.0-73.80_amd64.deb linux-image-5.15.0-74-generic_5.15.0-74.81_amd64.deb linux-image-5.15.0-75-generic_5.15.0-75.82_amd64.deb linux-image-5.15.0-77-generic_5.15.0-77.84_amd64.deb --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+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 2035163] Re: Avoid address overwrite in kernel_connect
** Description changed: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 + + + Testing: + - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. + + + Regression potenial: + - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. + + More information at: + https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => Khaled El Mously (kmously) -- 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2035163] [NEW] Avoid address overwrite in kernel_connect
Public bug reported: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Status in linux-gcp source package in Mantic: New Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2035163/+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 2034908] Re: Add support for 3 TDX subfeatures
** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) -- 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/2034908 Title: Add support for 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view Testing: Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. Regression potential: Most of the code changes are to the following files: arch/x86/coco/tdx drivers/virt/coco/tdx-guest/tdx-guest.c mm/memblock.c mm/memory_hotplug.c mm/page_alloc.c mm/vmstat.c Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" that affects many files and looks scary, but should be safe as it is basically a refactor. Generally speaking, the code changes here affect early memory initialization on x86 so can impact anything in that area, but realistically should only affect TDX instances (especially ones with >4GB as that is when the unaccepted-memory feature is activated). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2034908] Re: Add support for 3 TDX subfeatures
** Description changed: Support is requested for 3 TDX-specific features: - - Unaccepted memory, aka "lazy memory accept" - - TDX "Get Quote" - is needed for attestation - - Marking the TSC as reliable + - Unaccepted memory, aka "lazy memory accept" + - TDX "Get Quote" - is needed for attestation + - Marking the TSC as reliable + + More information at: + https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view - More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view + Testing: + Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. + GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. + + + Regression potential: + Most of the code changes are to the following files: + + arch/x86/coco/tdx + drivers/virt/coco/tdx-guest/tdx-guest.c + mm/memblock.c + mm/memory_hotplug.c + mm/page_alloc.c + mm/vmstat.c + + + Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY + + There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" + that affects many files and looks scary, but should be safe as it is + basically a refactor. + + Generally speaking, the code changes here affect early memory + initialization on x86 so can impact anything in that area, but + realistically should only affect TDX instances (especially ones with + >4GB as that is when the unaccepted-memory feature is activated). -- 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/2034908 Title: Add support for 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view Testing: Intel has provided code review for the first 2 and has additionally tested the GetQuote feature. GCP has tested all three features and confirmed basic functionality and sanity. More testing will follow when the changes are available in -proposed and before feature release. Regression potential: Most of the code changes are to the following files: arch/x86/coco/tdx drivers/virt/coco/tdx-guest/tdx-guest.c mm/memblock.c mm/memory_hotplug.c mm/page_alloc.c mm/vmstat.c Most of it is new code which is inside #ifdef CONFIG_UNACCEPTED_MEMORY There is 1 tree-wide change "mm, treewide: redefine MAX_ORDER sanely" that affects many files and looks scary, but should be safe as it is basically a refactor. Generally speaking, the code changes here affect early memory initialization on x86 so can impact anything in that area, but realistically should only affect TDX instances (especially ones with >4GB as that is when the unaccepted-memory feature is activated). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2034908] Re: Add support 3 TDX subfeatures
** Summary changed: - Support 3 TDX subfeatures + Add support 3 TDX subfeatures ** Summary changed: - Add support 3 TDX subfeatures + Add support for 3 TDX subfeatures -- 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/2034908 Title: Add support for 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2034908] [NEW] Support 3 TDX subfeatures
Public bug reported: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2034908 Title: Support 3 TDX subfeatures Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Lunar: New Bug description: Support is requested for 3 TDX-specific features: - Unaccepted memory, aka "lazy memory accept" - TDX "Get Quote" - is needed for attestation - Marking the TSC as reliable More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034908/+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 2034894] Re: Fix requested for SEV live-migration
** Description changed: The following upstream fix is requested to resolve issues with SEV live- migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view + Testing: + - Boot-tested each of f/gcp, j/gcp and l/gcp + - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. - Testing: - - Boot-tested each of f/gcp, j/gcp and l/gcp - - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. + + Regression potential: + - The change affects arch/x86/kernel/kvm.c so KVM on x86 can be impacted. It is a minimalistic change though, and regression risk is considered low. -- 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: In Progress Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: In Progress Status in linux-gcp source package in Mantic: In Progress Bug description: The following upstream fix is requested to resolve issues with SEV live-migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view Testing: - Boot-tested each of f/gcp, j/gcp and l/gcp - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. Regression potential: - The change affects arch/x86/kernel/kvm.c so KVM on x86 can be impacted. It is a minimalistic change though, and regression risk is considered low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034894/+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 2024500] Re: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration.
Hello @mloza1, Are you using AMD SEV here by any chance? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2024500 Title: KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration. Status in linux-hwe-5.15 package in Ubuntu: Confirmed Bug description: I have weird situation when I am live migrating a VM between two nodes, the VM hangs after migrating from EPYC3(Milan) to EPYC1(Naples) nodes. First node: CPU(s) AMD EPYC 7713 64-Core Processor (2 Sockets) Linux compute81 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Second node: CPU(s) AMD EPYC 7401 24-Core Processor (2 Sockets) Linux compute37 5.15.0-75-generic #82~20.04.1-Ubuntu SMP Wed Jun 7 19:37:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux When I am migrating from second type node to first type - everything works. When I am migrating from first type to second type - VM hangs No issues using the following kernels: 5.15.99 from upstream linux-image-5.15.0-25-generic_5.15.0-25.25_amd64 I'm able to reproduce the issue using the following kernels: linux-image-5.15.0-67-generic_5.15.0-67.74_amd64.deb linux-image-5.15.0-68-generic_5.15.0-68.75_amd64.deb linux-image-5.15.0-69-generic_5.15.0-69.76_amd64.deb linux-image-5.15.0-70-generic_5.15.0-70.77_amd64.deb linux-image-5.15.0-72-generic_5.15.0-72.79_amd64.deb linux-image-5.15.0-73-generic_5.15.0-73.80_amd64.deb linux-image-5.15.0-74-generic_5.15.0-74.81_amd64.deb linux-image-5.15.0-75-generic_5.15.0-75.82_amd64.deb linux-image-5.15.0-77-generic_5.15.0-77.84_amd64.deb --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 20 21:15 seq crw-rw 1 root audio 116, 33 Jun 20 21:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro AS -2124BT-HNTR Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-75-generic root=UUID=178395aa-ca05-47a1-9f4a-0696787bb100 ro rootflags=subvol=@ console=tty1 console=ttyS1,115200n8 ProcVersionSignature: Ubuntu 5.15.0-75.82~20.04.1-generic 5.15.99 RelatedPackageVersions: linux-restricted-modules-5.15.0-75-generic N/A linux-backports-modules-5.15.0-75-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/23/2022 dmi.bios.release: 5.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12DST-B dmi.board.vendor: Supermicro dmi.board.version: 1.00A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.5:bd09/23/2022:br5.22:svnSupermicro:pnAS-2124BT-HNTR:pvr0123456789:rvnSupermicro:rnH12DST-B:rvr1.00A:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2124BT-HNTR dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500/+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 2034894] Re: Fix requested for SEV live-migration
** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress -- 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: In Progress Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: In Progress Status in linux-gcp source package in Mantic: In Progress Bug description: The following upstream fix is requested to resolve issues with SEV live-migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view Testing: - Boot-tested each of f/gcp, j/gcp and l/gcp - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034894/+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 2034894] Re: Fix requested for SEV live-migration
** Description changed: The following upstream fix is requested to resolve issues with SEV live- migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view + + + Testing: + - Boot-tested each of f/gcp, j/gcp and l/gcp + - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. -- 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Bug description: The following upstream fix is requested to resolve issues with SEV live-migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view Testing: - Boot-tested each of f/gcp, j/gcp and l/gcp - GCP has tested each of them as well and reported that the live-migration issue under SEV gets resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034894/+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 2034894] [NEW] Fix requested for SEV live-migration
Public bug reported: The following upstream fix is requested to resolve issues with SEV live- migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New -- 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Lunar: New Bug description: The following upstream fix is requested to resolve issues with SEV live-migration: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=ac3f9c9f1b37edaa7d1a9b908bc79d843955a1a2 More details in: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2034894/+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 2033570] [NEW] Add support for Intel TDX features
Public bug reported: See SalesForce for more info: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view and also: https://bugs.launchpad.net/intel/+bug/1971028 https://bugs.launchpad.net/intel/+bug/2031044 https://bugs.launchpad.net/intel/+bug/2030895 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Description changed: See SalesForce for more info: - https://canonical.lightning.force.com/lightning/r/Case/5008e0HNdQ8AAL/view + https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view + + and also: + + https://bugs.launchpad.net/intel/+bug/1971028 + https://bugs.launchpad.net/intel/+bug/2031044 + https://bugs.launchpad.net/intel/+bug/2030895 ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => In Progress -- 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/2033570 Title: Add support for Intel TDX features Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Lunar: In Progress Bug description: See SalesForce for more info: https://canonical.lightning.force.com/lightning/r/Case/5008e0FTWGcAAP/view and also: https://bugs.launchpad.net/intel/+bug/1971028 https://bugs.launchpad.net/intel/+bug/2031044 https://bugs.launchpad.net/intel/+bug/2030895 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2033570/+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 2003053] Re: NFS: client permission error after adding user to permissible group
The kernels that are currently in -proposed should have resolved this issue. Kernel versions: 5.4.0-154.171 (focal) 5.15.0-77.84 (jammy) The new NFS behaviour has been made to be opt-in only using the "nfs_fasc=1" modprobe option. So default behaviour should be back to normal unless this option is used. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Incomplete Status in linux-gke package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Released Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
** Description changed: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from - upstream 6.2 to the 5.19 (kinetic) gcp kernel + upstream 6.2 to the 5.19 gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD hardware. ** Description changed: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD hardware. + - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD hardware. ** Description changed: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD hardware. + + + Regression potential: + - The changes are limited to the AMD iommu driver. Regression potential could impact virtualization on AMD hardware. Risk is considered low as the changes are limited and apply cleanly from upstream. ** Description changed: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD hardware. - Regression potential: - - The changes are limited to the AMD iommu driver. Regression potential could impact virtualization on AMD hardware. Risk is considered low as the changes are limited and apply cleanly from upstream. + - The changes are limited to the AMD iommu driver. Regression potential could impact virtualization on AMD hardware. Risk is considered low as the changes are limited and apply cleanly from upstream. The requested patch is from 6.2 and there have been no follow-up fixes since. -- 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/2023313 Title: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Kinetic: In Progress Bug description: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 gcp kernel The following two patches are
[Kernel-packages] [Bug 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
** Description changed: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 (kinetic) gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that this also has a security side-effect which they are interested in. + - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD hardware. -- 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/2023313 Title: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Kinetic: In Progress Bug description: GCP is requesting the backport of the patch "6b080c4e815ceba3c08f iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2 to the 5.19 (kinetic) gcp kernel The following two patches are required for the backport: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view Impact: - This allows the AMD iommu driver to map/unmap multiple pages in one call. GCP states that these changes also have a security side-effect which they are interested in. Testing: - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2023313/+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 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
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/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
Fix Committed
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+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 2023313] Re: gcp" backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
** Description changed:
GCP is asking for a backport of the patch "iommu/amd: Add
- map/unmap_pages() iommu_domain_ops callback support" to the 5.19
- (kinetic) gcp kernel
+ map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2
+ to the 5.19 (kinetic) gcp kernel
+
+ The following two patches are required for the backport:
+ 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement
map_pages io_pgtable_ops callback
+ 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement
unmap_pages io_pgtable_ops callback
+
+ More info at
+ https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
- The following two patches are pre-requisites:
- 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement
map_pages io_pgtable_ops callback
- 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement
unmap_pages io_pgtable_ops callback
+ Impact:
+ - This allows the AMD iommu driver to map/unmap multiple pages in one call.
GCP states that this also has a security side-effect which they are interested
in.
- More info at
https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
+ Testing:
+ - Boot-tested the change in a gcp SEV and non-SEV environment on AMD
hardware.
** Description changed:
GCP is asking for a backport of the patch "iommu/amd: Add
map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2
to the 5.19 (kinetic) gcp kernel
The following two patches are required for the backport:
6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement
map_pages io_pgtable_ops callback
251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement
unmap_pages io_pgtable_ops callback
More info at
https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
-
Impact:
- - This allows the AMD iommu driver to map/unmap multiple pages in one call.
GCP states that this also has a security side-effect which they are interested
in.
-
+ - This allows the AMD iommu driver to map/unmap multiple pages in one call.
GCP states that this also has a security side-effect which they are interested
in.
Testing:
- - Boot-tested the change in a gcp SEV and non-SEV environment on AMD
hardware.
+ - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD
hardware.
** Also affects: linux-gcp (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux-gcp (Ubuntu Kinetic)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux-gcp (Ubuntu)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux-gcp (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu)
Status: New => In Progress
** Summary changed:
- gcp" backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback
support"
+ gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback
support"
** Description changed:
- GCP is asking for a backport of the patch "iommu/amd: Add
- map/unmap_pages() iommu_domain_ops callback support" from upstream 6.2
- to the 5.19 (kinetic) gcp kernel
+ GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
+ iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
+ upstream 6.2 to the 5.19 (kinetic) gcp kernel
The following two patches are required for the backport:
6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement
map_pages io_pgtable_ops callback
251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement
unmap_pages io_pgtable_ops callback
More info at
https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
Impact:
- This allows the AMD iommu driver to map/unmap multiple pages in one call.
GCP states that this also has a security side-effect which they are interested
in.
Testing:
- Boot-tested the changes in a gcp SEV and non-SEV environment on AMD
hardware.
--
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/2023313
Title:
gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops
callback support"
Status in linux-gcp package in Ubuntu:
In Progress
Status in linux-gcp source package in Kinetic:
In Progress
Bug description:
GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
from upstream 6.2 to the 5.19 (kinetic) gcp kernel
The following two patches are required for the backport:
[Kernel-packages] [Bug 2023313] [NEW] gcp" backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
Public bug reported: GCP is asking for a backport of the patch "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" to the 5.19 (kinetic) gcp kernel The following two patches are pre-requisites: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- 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/2023313 Title: gcp" backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" Status in linux-gcp package in Ubuntu: New Bug description: GCP is asking for a backport of the patch "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" to the 5.19 (kinetic) gcp kernel The following two patches are pre-requisites: 6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback 251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback More info at https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2023313/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- 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/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013198/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Incomplete Status in linux-gke package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux-gke source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-gke source package in Jammy: Fix Committed Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Incomplete Status in linux-gke package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-gke source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux-gke source package in Jammy: Fix Committed Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Changed in: linux-gcp (Ubuntu Kinetic)
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/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
Fix Committed
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Changed in: linux-gke (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: Fix Committed Status in linux-gke source package in Jammy: Fix Committed Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Description changed: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. + The solution to this issue, at least temporarily and at least for linux- + gke, is to make the new behaviour optional using the "nfs_fasc=1" module + parameter. Without this parameter specified, (or specified as =0) will + keep the old behaviour. - The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. + + Regresion potential: + - Regression potential is considered low considering the scope of the change and is limited to NFS only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+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 2022098] Re: Severe NFS performance degradation after LP #2003053
** Description changed: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. + + + The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+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 2022098] [NEW] Severe NFS performance degradation after LP #2003053
Public bug reported: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. ** Affects: linux-gke (Ubuntu) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gke (Ubuntu Jammy) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-gke (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-gke (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+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 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Changed in: linux-gcp (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu)
Assignee: (unassigned) => Khaled El Mously (kmously)
** Changed in: linux-gcp (Ubuntu Kinetic)
Assignee: (unassigned) => Khaled El Mously (kmously)
--
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/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
New
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+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 2021830] [NEW] GVE: Performance improvement for "jumbo" frames
Public bug reported:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and is
being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
** Affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-gcp (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: debootstrap (Ubuntu)
** Also affects: linux-gcp (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
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/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
New
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013198/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** No longer affects: linux (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux source package in Kinetic: New Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013198/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu Kinetic) ** No longer affects: linux-gcp (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013198/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** No longer affects: linux-oracle (Ubuntu Jammy) ** No longer affects: linux-oracle (Ubuntu Kinetic) ** No longer affects: linux-oracle (Ubuntu Lunar) ** No longer affects: linux-gcp (Ubuntu Kinetic) ** No longer affects: linux-gcp (Ubuntu Lunar) -- 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/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as an EIO. User space > may continue to issue requests, even if it is unsafe to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2013198/+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 2011616] Re: Connection timeout due to conntrack limits
This issue was originally reported on GKE and verified by the GKE team. We do not have reproduction steps. As it is a change from upstream and a simple constant change, and since it is has already been verified on GKE, I am verifying it on GCP by code inspection. ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 2013198] Re: Fix (+follow-up) needed for SEV-SNP vulnerability
** Description changed: - See email about SEV-SNP guest attestation + From email discussions with Dionna Glazee from Google: + + + > This email details a critical vulnerability in SEV-SNP attestation + > report integrity protection that must be patched in SEV-SNP-enabled + > kernels. + > + > I'm reaching out since I've been tracking our progress towards a + > stable offering of customer access to SEV-SNP "guest requests". I'd + > like to know how or if y'all test the /dev/sev-guest driver. + > + > The reason I ask is because our host KVM injects failures into the + > guest if requests come too frequently. Test suites that request + > attestation reports in quick succession will fail without very recent + > patches or workaround code in user space. + > + > Technical details, tl;dr + > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa + > that will cause attestation to fail frequently (in GCE). Peter found + > and patched this vulnerability. + > + > Details of security patch 47894e0fa: + > This patch to sev-guest causes more fail-closed situations. All VMM + > errors other than INVALID_LEN will wipe out the VMPCK and close the + > guest's ability to communicate with the security processor. + > Ratelimit failures will also cause a fail-closed situation. + > + > As you may know, guest requests are encrypted by the guest with + > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory + > to the host's KVM. KVM forwards that to the crypto/ccp driver to + > deliver to the AMD secure processor to respond to. When the VMM + > returns an error instead of forwarding a request to the secure + > processor, then the guest driver *does not* increment its IV. It can + > therefore reuse an IV on multiple messages with different contents. + > This breaks AES_GCM's security guarantees. + > + > Ratelimiting looks to the guest not as a stalled vCPU, but rather a + > special error response that AMD will include in their next published + > version of the GHCB protocol (I believe v2.02). This allows the guest + > VM to schedule other threads and remain productive while waiting up to + > 2 seconds for a request to be serviced. The special error code to an + > unpatched kernel is just forwarded to the guest as an EIO. User space + > may continue to issue requests, even if it is unsafe to do so. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Jammy: New Status in linux-oracle source package in Kinetic: New Status in linux-oracle source package in Lunar: New Bug description: From email discussions with Dionna Glazee from Google: > This email details a critical vulnerability in SEV-SNP attestation > report integrity protection that must be patched in SEV-SNP-enabled > kernels. > > I'm reaching out since I've been tracking our progress towards a > stable offering of customer access to SEV-SNP "guest requests". I'd > like to know how or if y'all test the /dev/sev-guest driver. > > The reason I ask is because our host KVM injects failures into the > guest if requests come too frequently. Test suites that request > attestation reports in quick succession will fail without very recent > patches or workaround code in user space. > > Technical details, tl;dr > * Nov 21, 2022: Linux Kernel 6.1 included a security patch 47894e0fa > that will cause attestation to fail frequently (in GCE). Peter found > and patched this vulnerability. > > Details of security patch 47894e0fa: > This patch to sev-guest causes more fail-closed situations. All VMM > errors other than INVALID_LEN will wipe out the VMPCK and close the > guest's ability to communicate with the security processor. > Ratelimit failures will also cause a fail-closed situation. > > As you may know, guest requests are encrypted by the guest with > AES_GCM (not AES_GCM_SIV) and then passed through unencrypted memory > to the host's KVM. KVM forwards that to the crypto/ccp driver to > deliver to the AMD secure processor to respond to. When the VMM > returns an error instead of forwarding a request to the secure > processor, then the guest driver *does not* increment its IV. It can > therefore reuse an IV on multiple messages with different contents. > This breaks AES_GCM's security guarantees. > > Ratelimiting looks to the guest not as a stalled vCPU, but rather a > special error response that AMD will include in their next published > version of the GHCB protocol (I believe v2.02). This allows the guest > VM to schedule other threads and remain productive while waiting up to > 2 seconds for a request to be serviced. The special error code to an > unpatched kernel is just forwarded to the guest as
[Kernel-packages] [Bug 2013198] [NEW] Fix (+follow-up) needed for SEV-SNP vulnerability
Public bug reported: See email about SEV-SNP guest attestation ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** Also affects: linux-oracle (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2013198 Title: Fix (+follow-up) needed for SEV-SNP vulnerability Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Jammy: New Status in linux-oracle source package in Kinetic: New Status in linux-oracle source package in Lunar: New Bug description: See email about SEV-SNP guest attestation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2013198/+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 2011616] Re: Connection timeout due to conntract limits
** Description changed: - Customers of GKE 1.25 and 1.26 are affected by the connack performance + Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 ** Summary changed: - Connection timeout due to conntract limits + Connection timeout due to conntrack limits -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: Incomplete Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 2011616] [NEW] Connection timeout due to conntract limits
Public bug reported: Customers of GKE 1.25 and 1.26 are affected by the connack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntract limits Status in linux package in Ubuntu: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the connack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+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 2003816] Re: Regression in ext4 during online resize
Verified the issue is no longer reproducible on linux-aws Ubuntu- aws-5.15.0-1031.35 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+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 2003816] [NEW] Regression in ext4 during online resize
Public bug reported: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** No longer affects: linux-oracle (Ubuntu Jammy) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu) ** No longer affects: linux-aws (Ubuntu Jammy) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+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 2002381] Re: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
This was requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view ** Changed in: linux-oracle (Ubuntu) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+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 2002381] Re: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
LP #1925421 is the main arm64 enablement bug - this is just a follow-up -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+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 2002381] [NEW] arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle
Public bug reported: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: In Progress ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2002381 Title: arm64 support: Enable ARM_SMMU and ARM_SMMU_V3 for oracle Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Focal: In Progress Bug description: The ARM_SMMU and ARM_SMMU_V3 kernel options should be enabled as requested in https://canonical.lightning.force.com/lightning/r/Case/5004K0OlOPXQA3/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2002381/+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 2001605] Re: Add support for SEV-SNP
** Description changed: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in v5.19 with some prerequisites from v5.16. This feature is requested to be backported to Jammy (5.15). + + + More information at https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view ** Description changed: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in v5.19 with some prerequisites from v5.16. This feature is requested to be backported to Jammy (5.15). + More information at + https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view - More information at https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view + + [Impact] + No support for SEV-SNP on AMD EPYC2 CPUs currently + + [Fix] + Add SEV-SNP support patches. + + [Test] + Extensive testing by the cloud team over several months, testing general functionality under SEV-SNP. + + [Regression Potential] + This was never working so there should be no risk of regression for SEV-SNP.As it does change those files it can have an effect on existing SEV functionality in case of a bug. The code is limited so no regression outside of SEV is expected. -- 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/2001605 Title: Add support for SEV-SNP Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in v5.19 with some prerequisites from v5.16. This feature is requested to be backported to Jammy (5.15). More information at https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view [Impact] No support for SEV-SNP on AMD EPYC2 CPUs currently [Fix] Add SEV-SNP support patches. [Test] Extensive testing by the cloud team over several months, testing general functionality under SEV-SNP. [Regression Potential] This was never working so there should be no risk of regression for SEV-SNP.As it does change those files it can have an effect on existing SEV functionality in case of a bug. The code is limited so no regression outside of SEV is expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2001605/+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 2001605] [NEW] Add support for SEV-SNP
Public bug reported: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in v5.19 with some prerequisites from v5.16. This feature is requested to be backported to Jammy (5.15). More information at https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu) ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in - v5.19 with some prerequisites from v5.16 + v5.19 with some prerequisites from v5.16. This feature is requested to + be backported to Jammy (5.15). -- 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/2001605 Title: Add support for SEV-SNP Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: Version 3 of AMD's Secure Encrypted Virtualization is called SNP (Secure Nested Pages). Support for this has been added to the kernel, mostly in v5.19 with some prerequisites from v5.16. This feature is requested to be backported to Jammy (5.15). More information at https://canonical.lightning.force.com/lightning/r/Case/5004K0EA2meQAD/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2001605/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
haha -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/401 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
Khaled El Mously (khalid.elmou...@canonical.com) has submted a patchset for this bug: https://cktreview.org/r/c/dummy/+/381 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
hello -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1810488] Re: Dummy bug for testing (please ignore)
hello long time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810488 Title: Dummy bug for testing (please ignore) Status in linux package in Ubuntu: Invalid Bug description: I'm using this dummy bug to test some command-line/launchpad scripts/ and tools - please ignore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810488/+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 1953575] Re: Update gvnic driver code
** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Released Status in linux-gcp source package in Impish: Fix Released Status in linux-gcp source package in Jammy: New Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+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 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Was audio working previously on this hardware and then stopped after a kernel (or other package) update? If so, we can try bisecting. Note also that the 5.15.0-41.44 kernel has been out for a while now. The most recent kernel is 5.15.0-48.54 so maybe that is worth trying as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1984034] Re: Backport patches needed to allow live migration under SEV
https://lists.ubuntu.com/archives/kernel-team/2022-August/132504.html https://lists.ubuntu.com/archives/kernel-team/2022-August/132508.html Patches have been sent to mailing list and applied. -- 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/1984034 Title: Backport patches needed to allow live migration under SEV Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. [Impact] No support for live-migration of confidential VMs currently [Fix] Backport 5 patches from v5.16 [Test] GCP confirmed that live-migration works with these patches. [Regression Potential] This was never working so there should be low risk of regression. Most of the changes are KVM-related so could have an impact on KVM. However most of the changes are new code so risk is low. More details in the SF case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+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 1984034] Re: Backport patches needed to allow live migration under SEV
** Description changed: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. + [Impact] + No support for live-migration of confidential VMs currently + + [Fix] + Backport 5 patches from v5.16 + + [Test] + GCP confirmed that live-migration works with these patches. + + [Regression Potential] + This was never working so there should be low risk of regression. + Most of the changes are KVM-related so could have an impact on KVM. + However most of the changes are new code so risk is low. + + More details in the SF case. -- 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/1984034 Title: Backport patches needed to allow live migration under SEV Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. [Impact] No support for live-migration of confidential VMs currently [Fix] Backport 5 patches from v5.16 [Test] GCP confirmed that live-migration works with these patches. [Regression Potential] This was never working so there should be low risk of regression. Most of the changes are KVM-related so could have an impact on KVM. However most of the changes are new code so risk is low. More details in the SF case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+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 1984034] [NEW] Backport patches needed to allow live migration under SEV
Public bug reported: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. More details in the SF case. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: - https://canonical.lightning.force.com/lightning/r/Case/5004K09oeuIQAQ/ + https://canonical.my.salesforce.com/5004K09oeuI - Upstream (v5.16 mostly) patches needed to allow live migration of - confidential VMs. + Upstream (v5.16) patches needed to allow live migration of confidential + VMs. More details in the SF case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1984034 Title: Backport patches needed to allow live migration under SEV Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. More details in the SF case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+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 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Hi @Louis.. Could you please try to reproduce this issue on the latest Jammy images with a 5.15 kernel? (The 5.13 kernel is EOL). I have tried to reproduce the issue myself on a BM.Standard.E3.128 instance, but I am not sure exactly how to launch the VM correctly with SEV enabled. If you could provide instructions that would be very helpful. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in grub2 source package in Impish: Confirmed Status in linux source package in Impish: Invalid Status in grub2 source package in Jammy: Confirmed Status in linux source package in Jammy: Invalid Bug description: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144). Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it fails and later trigger a kernel panic with the following trace : $ grep TLB /tmp/console.log [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.034219] kvm-guest: KVM setup pv remote TLB flush [0.037063] software IO TLB: Cannot allocate buffer [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.019552] software IO TLB: No low mem [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- The SWIOTLB adjustment comes from the following kernel commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 For some reason, the LowMem allocation fails (as seen by the "software IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be completed. When booting with the swiotlb=262144 value, we get the following output : $ grep TLB /tmp/console.log [0.050908] kvm-guest: KVM setup pv remote TLB flush [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.071837] software IO TLB: mapped [mem 0x5bebe000-0x7bebe000] (512MB) [1.529804] software IO TLB: Memory encryption is active and system is using DMA bounce buffers For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without the need to set the swiotlb= value at boot time. The SWIOTLB buffer adjustment has been introduced in kernel 5.11. We can make SEV enabled resources available for testing if needed. ...Louis --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 23 13:32 seq crw-rw 1 root audio 116, 33 Dec 23 13:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Scaleway SCW-ENT1-S Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A
[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hey Zhanglei. We do not have a 5.16 Ubuntu kernel. We do have 5.15 kernels. The current mainline version is 5.18 not 5.16. I have built 2 kernels, one 5.18 and one 5.15 kernel for you. 5.15: https://kernel.ubuntu.com/~kmously/kernel-kmously-45afdcc-gwrv/ 5.18: https://kernel.ubuntu.com/~kmously/kernel-kmously-469ac56-or1l/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. Great. We have identified the problem patch, which is this one: 380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile But I am not really sure why this patch is causing a problem. The patch only adds one new line as you can see here: https://pastebin.ubuntu.com/p/TDXdRttc4M/plain Looks like it is altering the behaviour of "PCI device ID 1022:7901" which is supposed to be AMD "Green Sardine". From what I found online, "Green Sardine" is an AMD APU (CPU + GPU) but I believe you are using an AMD EPYC server, so I don't understand why you would be affected at all. Looking at the SOS report you provided, I see the device ID for the SATA controller is 1022:7901 even though you are using EPYC. Again, not really sure why. I don't understand why there is a conflict in device IDs like this. I will see if I can find out more information. Do you know if the problem happens with any disk you hotplug, or just this one? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks. This means: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG 3005: BUG 3006: NO BUG There are only 5 patches between 3005 and 3006 so one of them is the problem. You can see the list of patches here: https://pastebin.canonical.com/p/TkvDGcfHWk/plain/ Only one of them seems related to sata which is "ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile" So maybe this is the one. Please test kernel 3007 from here: https://kernel.ubuntu.com/~kmously/kernel-kmously-3b63e74-Mkii/ If this fails, then this will be the last kernel we have to test. Please make sure you are running version 3007. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks for the update. This means: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG 3005: BUG We are getting very close now. Please try version 3006 from this link: https://kernel.ubuntu.com/~kmously/kernel-kmously-c756bab-RGcD/ Please make sure you are running 3006. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello again Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG 3004: NO BUG You can find kernel 3005 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-039f206-aRqC/ Please ensure you are running version -3005. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. I am building 3005 now. It should be ready in about 30 minutes. I will update again soon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Fix Released Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Thanks Zhanglei. This means that so far: 3000: BUG 3002: NO BUG 3003: NO BUG We are getting closer. This is the remaining set of patches: 00501b41aaf73f (tag: test-3000, tag: fail1) s390/pci: move pseudo-MMIO to prevent MIO overlap 14914e943b0ca5 cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink() 02a3dc73620247 rt2x00: do not mark device gone on EPROTO errors during start d0c736f3c95a8e kprobes: Limit max data_size of the kretprobe instances 1101e48029ef8b vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit 8ac948debe102a net/smc: Avoid warning of possible recursive locking 844b74044432ab perf report: Fix memory leaks around perf_tip() ef0a82700dd088 perf hist: Fix memory leak of a perf_hpp_fmt 25b5451cf6b834 net: ethernet: dec: tulip: de4x5: fix possible array overflows in type3_infoblock() 79ab9e40571039 net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound 60cbd2bb3e4920 ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() 380cd49e207ba4 ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile 02ce9dcd0056d0 scsi: iscsi: Unblock session then wake up error handler 39fe9db370a672 thermal: core: Reset previous low and high trip during thermal zone init 9c4257be2b4e87 (tag: test-3004) btrfs: check-integrity: fix a warning on write caching disabled disk 7888748df21e65 s390/setup: avoid using memblock_enforce_memory_limit ec02be4afbaa32 platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep ecaf617d2d911f net: return correct error code cf471f304c7bdd atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait ef48e7dac2b4a5 net/smc: Transfer remaining wait queue entries during fallback f5a7ae1664ea55 mac80211: do not access the IV when it was stripped 04e2506c0a0f0e drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY cc02a02a96d745 gfs2: Fix length of holes reported at end-of-file db58cf66b9ed5f can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM 5891df6f755bdc arm64: dts: mcbin: support 2W SFP modules e7ef1451808ba8 of: clk: Make self-contained a8e84f43323809 NFSv42: Fix pagecache invalidation after COPY/CLONE 87243d366e21dd UBUNTU: upstream stable to v5.4.163 8dedcf4867336b Linux 5.4.163 fe61be970fa57f tty: hvc: replace BUG_ON() with negative return value ae65528da134f8 (tag: test-3003, tag: pass2) xen/netfront: don't trust the backend response data blindly The bottom commit (3003) passed and the top commit (3000) failed, so the problem is one of the patches in between. We are now about to test kernel 3004 in the middle. You can find kernel 3004 here: https://kernel.ubuntu.com/~kmously/kernel-kmously-721de44-fWzO/ Please ensure you are running version -3004. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei. Thanks for the update. >From my understanding, so far: 3000: BUG 3002: NO BUG I have the next kernel, 3003, available here: https://kernel.ubuntu.com/~kmously/kernel-kmously-8243717-Kutu Once again, please ensure that you are testing with -3003 when testing. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei, Thanks for the update. I am a little surprised that this kernel failed. There are 2 SATA related changes in kernel -100 which I suspected were the root cause. However, the kernel that I provided (version 3000) did NOT contain those patches, so I expected it to work. The patches that I suspected were the cause are: sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl In any case, maybe my assumption was incorrect. We can continue to bisect anyway. I am unable to provide all the kernels in one shot because the next kernel that we should test depends on the results of the test before it. If I give them all in one shot, I would have to give you 270 kernels to test instead of 9. We have already done the first bisect. Now we have 125 patches (instead of 270) so should be another 7 tests at most. The next kernel is available here: https://kernel.ubuntu.com/~kmously/kernel-kmously-440f762-4e4H/ This is version 3002. Please, when the engineer tests this kernel, make sure to type "uname -r" to confirm that it is version 3002. That way we can be 100% sure we are testing the right kernel. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server
Hello Zhanglei, thanks for confirming the working/broken versions. I am not sure if I will be able to reproduce the issue myself. There are 270 changes between -99 and -100. If you can help me bisect them, we should be able to quickly identify the problem. Would you be able to test the kernels I provide so we can identify the breaking commit? We might need to test up to 9 more kernels. I have built the first test kernel. It can be found at: https://kernel.ubuntu.com/~kmously/kernel-kmously-d60b65f-bspU/ If you can, please install the linux-image, linux-modules and linux- modules-extra packages from the above link and attempt to reproduce the problem. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EPYC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1971576] Re: SATA device hot plug regression on AMD EYPC (Asus) server
Hello @zhanglei-mao thanks for creating the bug report. There is a large time difference between those 5.4 kernels. 5.4.0-42 is from June 2020 and 5.4.0-109 is very recent. Is it possible to find out the first non-working 5.4 kernel? We would need to do a bisect. Do you think you might be able to test the 5.4.0-75 kernel to try to reproduce this problem? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971576 Title: SATA device hot plug regression on AMD EYPC (Asus) server Status in linux package in Ubuntu: Confirmed Bug description: SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux version 5.4.0-109-generic", but it works on earlier version of " Linux version 5.4.0-42-generic" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971576/+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 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
The change for this bug has been committed to the gcp kernel. The next focal/linux-gcp kernel release (5.4.0-1073 or later) should contain the updated configuration. The bionic/linux-gcp-5.4 kernel will receive the update as well. Thanks for reporting the issue, @lhaley, and thanks for your patience! -- 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/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Fix Committed Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => 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/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Fix Committed Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1964527] Re: Enable CONFIG_UNICODE for linux-gcp
** Changed in: linux-gcp (Ubuntu Focal) Status: Confirmed => In Progress -- 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/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: In Progress Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1925421] Re: arm64 support
** No longer affects: linux-gcp (Ubuntu Bionic) -- 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/1925421 Title: arm64 support Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: Fix Released Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+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 1925421] Re: arm64 support
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu Groovy) ** No longer affects: linux-gcp (Ubuntu Hirsute) ** No longer affects: linux-gcp (Ubuntu Impish) -- 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/1925421 Title: arm64 support Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: New Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: Fix Released Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+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 1965075] Re: arm64 suport
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** No longer affects: linux-oracle (Ubuntu Bionic) ** No longer affects: linux-oracle (Ubuntu Focal) ** No longer affects: linux-oracle (Ubuntu Jammy) -- 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/1965075 Title: arm64 suport Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1965075/+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 1965075] [NEW] arm64 suport
Public bug reported: [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1965075 Title: arm64 suport Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Bionic: New Status in linux-oracle source package in Focal: New Status in linux-oracle source package in Jammy: New Bug description: [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1965075/+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 1964527] [NEW] Enable CONFIG_UNICODE for linux-gcp
Public bug reported: See https://lists.ubuntu.com/archives/kernel-team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- 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/1964527 Title: Enable CONFIG_UNICODE for linux-gcp Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Bug description: See https://lists.ubuntu.com/archives/kernel- team/2022-March/128565.html NOTE: This config is enabled in other gcp kernels and in non-gcp kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1964527/+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 1953575] Re: Update gvnic driver code
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Impish: Fix Committed Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+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 1953575] Re: Update gvnic driver code
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Impish: Fix Committed Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+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 1953575] Re: Update gvnic driver code
** Also affects: linux-gcp (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Impish) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Impish) Status: New => In Progress -- 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/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: In Progress Status in linux-gcp source package in Impish: In Progress Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+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 1957744] Re: Unable to set correct resolutions on virtual displays
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish ** Tags removed: verification-needed-focal ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1957744 Title: Unable to set correct resolutions on virtual displays Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Hirsute: New Status in linux-oracle source package in Impish: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1957744/+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 1959173] Re: Vulnerability in af_packet handling
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Focal: In Progress Bug description: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+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 1959173] [NEW] Vulnerability in af_packet handling
Public bug reported: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 ** Affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1959173 Title: Vulnerability in af_packet handling Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Bug description: CVE-2021-22600 A vulnerability, which was classified as critical, was found in Linux Kernel. Affected is the function packet_set_ring of the file net/packet/af_packet.c. The manipulation with an unknown input leads to a memory corruption vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The weakness was released 01/26/2022. The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2021-22600 since 01/05/2021. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 01/26/2022). Applying a patch is able to eliminate this problem. The fix is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 More information at: https://partnerissuetracker.corp.google.com/issues/215427453 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1959173/+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 1957744] [NEW] Unable to set correct resolutions on virtual displays
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Also affects: linux-oracle (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1957744 Title: Unable to set correct resolutions on virtual displays Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Hirsute: New Status in linux-oracle source package in Impish: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view for more info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1957744/+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 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Hello @Louis, Are you able to confirm whether the 4.15 kernels are affected by this problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Bug description: [Impact] The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 Author: Lenny Szubowicz Date: Fri Sep 4 21:31:05 2020 -0400 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. [Test case] The kernel need to boot properly with SEV enabled. [Potential regression] The fix is very specific and restricted and should cause regressions, however it touches ioremap that is widely used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
I'm not sure I see a panic in the attached kernel log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param Status in linux package in Ubuntu: Confirmed Bug description: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144). Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it fails and later trigger a kernel panic with the following trace : $ grep TLB /tmp/console.log [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.034219] kvm-guest: KVM setup pv remote TLB flush [0.037063] software IO TLB: Cannot allocate buffer [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.019552] software IO TLB: No low mem [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- The SWIOTLB adjustment comes from the following kernel commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 For some reason, the LowMem allocation fails (as seen by the "software IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be completed. When booting with the swiotlb=262144 value, we get the following output : $ grep TLB /tmp/console.log [0.050908] kvm-guest: KVM setup pv remote TLB flush [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.071837] software IO TLB: mapped [mem 0x5bebe000-0x7bebe000] (512MB) [1.529804] software IO TLB: Memory encryption is active and system is using DMA bounce buffers For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without the need to set the swiotlb= value at boot time. The SWIOTLB buffer adjustment has been introduced in kernel 5.11. We can make SEV enabled resources available for testing if needed. ...Louis --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 23 13:32 seq crw-rw 1 root audio 116, 33 Dec 23 13:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Scaleway SCW-ENT1-S Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.0 dmi.modalias:
[Kernel-packages] [Bug 1953575] [NEW] Update gvnic driver code
Public bug reported: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool ** Affects: linux-gcp (Ubuntu) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Assignee: Khaled El Mously (kmously) Status: In Progress ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: klibc (Ubuntu) ** Description changed: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. + + + [Impact] + Missing functionality from the Google gvnic driver + + + [Test Plan] + Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE + + + [Regression potential] + Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. + + + + List of changes: + + 3712db620c613 gve: DQO: Configure interrupts on device up + a9fd7559a367a gve: Check TX QPL was actually assigned + c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check + f48adc2842b17 gve: DQO: Remove incorrect prefetch + 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API + 56c0904d8491d gve: Propagate error codes to caller + 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() + ea364622fb118 gve: Fix warnings reported for DQO patchset + 8890e8783c6e6 gve: DQO: Add RX path + abfc55f80d423 gve: DQO: Add TX path + ef63867982913 gve: DQO: Add ring allocation and initialization + dc3e0aef11bf0 gve: DQO: Add core netdev features + 873fd9825efd7 gve: Update adminq commands to support DQO queues + 543dc0e670472 gve: Add DQO fields for core data structures + b580730931348 gve: Add dqo descriptors + 74e123d3c62b2 gve: Add support for DQO RX PTYPE map + a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic + 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` + a6b09c93c1735 gve: Introduce a new model for device options + 34d6b75678979 gve: Add support for raw addressing in the tx path + 30b6221596699 Revert "gve: Check TX QPL was actually assigned" + 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset + ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument + 5fc5c482008b5 gve: Move some static functions to a common file + ed1e0daeee1ac gve:
[Kernel-packages] [Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Found on: 2021.09.27/bionic/linux-gcp-4.15/4.15.0-1110.124 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux-oracle source package in Xenial: New Status in linux source package in Bionic: Incomplete Status in linux-oracle source package in Bionic: New Bug description: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+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 1945559] Re: Failed to start Kernel Modules and small Ubuntu resolution
@Muhammed: It may be a good idea also to try a fresh Ubuntu 18.04 installation inside a different VM (with the same exact settings as this one) to see if it has the same issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945559 Title: Failed to start Kernel Modules and small Ubuntu resolution Status in linux package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Dear Experts, I updated ubuntu from 16.04 to 18.04 in vBox 6.1. There are two issues now. 1) In the start, a message is displaying: "[Failed] Failed to start Load Kernel Modules". Please see hostnamectl command display below. 2) A small ubuntu screen displays in the middle, looks like a resolution issue. I tried VBoxVGA, VMSVGA, VBoxSVGA. For VBoxSVGA, sometimes it works and full screen displays but sometimes it doesn't. Are both 1,2 are correlated and now we can solve it? Thanks, Muhammad muhammad@gul:~$ hostnamectl Static hostname: gul Icon name: computer-vm Chassis: vm Machine ID: 9fb1265c43101e08a30348bb551096be Boot ID: 8ffe16ad10064fc094583e7b11a88c0d Virtualization: oracle Operating System: Ubuntu 18.04.6 LTS Kernel: Linux 4.15.0-160-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945559/+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 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] - The following upstream patches address this: + The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors -- 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/1943902 Title: NVME errors in confidential vms Status in linux-gcp package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: New Status in linux-gcp-5.4 source package in Bionic: New Status in linux-gcp source package in Focal: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches from v5.12 address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] Low risk as the patches are mostly clean-up and refactor. Regression in swiotlb could cause hardware read/write errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1943902/+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 1943902] Re: NVME errors in confidential vms
** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. - + Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define - [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command - line, and an additional swiotlb nvme device attached: + line, and an additional nvme device attached: - $ sudo mkfs.xfs -f /dev/nvme2n1 - meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks - = sectsz=512 attr=2, projid32bit=1 - = crc=1finobt=1, sparse=0, rmapbt=0, refl - ink=0 - data = bsize=4096 blocks=524288, imaxpct=25 - = sunit=0 swidth=0 blks - naming =version 2 bsize=4096 ascii-ci=0 ftype=1 - log =internal log bsize=4096 blocks=2560, version=2 - = sectsz=512 sunit=0 blks, lazy-count=1 - realtime =none extsz=4096 blocks=0, rtextents=0 + $ sudo mkfs.xfs -f /dev/nvme2n1 + meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks + = sectsz=512 attr=2, projid32bit=1 + = crc=1finobt=1, sparse=0, rmapbt=0, refl + ink=0 + data = bsize=4096 blocks=524288, imaxpct=25 + = sunit=0 swidth=0 blks + naming =version 2 bsize=4096 ascii-ci=0 ftype=1 + log =internal log bsize=4096 blocks=2560, version=2 + = sectsz=512 sunit=0 blks, lazy-count=1 + realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error - Note the input/output error The error no longer happens with the fixes applied. + [Regression Potential] + + Low risk as the patches are mostly clean-up and refactor. + Regression in swiotlb could cause hardware read/write errors ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oracle (Ubuntu) ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gcp-5.4 (Ubuntu Focal) ** No longer affects: linux-gcp (Ubuntu Bionic) ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gcp-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Khaled El Mously (kmously) ** Description changed: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] - Using nvme hardware that uses in confidential VMs can encounter hardware read/write errors. + Using nvme with swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, p
[Kernel-packages] [Bug 1943902] [NEW] NVME errors in confidential vms
Public bug reported: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1943902 Title: NVME errors in confidential vms Status in linux-oracle package in Ubuntu: New Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view for more info [Impact] Using nvme hardware that uses swiotlb in confidential VMs can encounter hardware read/write errors. [Fix] The following upstream patches address this: 3d2d861eb03e nvme-pci: set min_align_mask 1f221a0d0dbf swiotlb: respect min_align_mask 16fc3cef33a0 swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single 26a7e094783d swiotlb: refactor swiotlb_tbl_map_single ca10d0f8e530 swiotlb: clean up swiotlb_tbl_unmap_single c32a77fd1878 swiotlb: factor out a nr_slots helper c7fbeca757fe swiotlb: factor out an io_tlb_offset helper b5d7ccb7aac3 swiotlb: add a IO_TLB_SIZE define [Test] Using a confidential VM, with 'swiotlb=force' set on the kernel command line, and an additional swiotlb nvme device attached: $ sudo mkfs.xfs -f /dev/nvme2n1 meta-data=/dev/nvme2n1 isize=512agcount=4, agsize=131072 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, refl ink=0 data = bsize=4096 blocks=524288, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 mkfs.xfs: pwrite failed: Input/output error Note the input/output error The error no longer happens with the fixes applied. [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1943902/+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 1925421] Re: arm64 support
** Tags removed: verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: In Progress Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+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 1840488] Re: Disable Bluetooth in cloud kernels
** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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
