[Kernel-packages] [Bug 2052451] [NEW] Incorrect argument to notify_page_enc_status_changed()
Public bug reported: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * Include change from upstream 064ce6c550a06 [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) 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/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * Include change from upstream 064ce6c550a06 [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Description changed: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] - * Include change from upstream 064ce6c550a06 + * 27ba8c7 modified notify_page_enc_status_changed(), when it should not + have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. -- 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/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2052469] [NEW] Provide an arm64 linux-oracle 64k kernel variant
Public bug reported: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 ** Affects: linux-oracle (Ubuntu) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Affects: linux-oracle (Ubuntu Noble) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Also affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-oracle (Ubuntu Noble) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Mantic: In Progress Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) 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/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: In Progress Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) 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/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2052576] [NEW] GCP TDX Support
Public bug reported: [Impact] * Google requested TDX guest features. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00363309 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) 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/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Google requested TDX guest features. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+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 2052576] Re: GCP TDX Support
** Description changed: [Impact] - * Google requested TDX guest features. + * Google requested TDX guest features to be added to GCP kernel. [Fix] - * Add flavour and configs for 64k flavour + * 16 clean cherry-picks from upstream + * 2 backports from upstream + * 11 backports from Intel + * 1 config change to enable support [Test Case] * Compile tested * Boot tested + * Tested internally at various stages of development * Tested by Google [Where things could go wrong] - * Low chance of regression. Isolated logic fix. + * Majority of patches come from upstream with minimal backporting. + * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 ** Description changed: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] - * 16 clean cherry-picks from upstream - * 2 backports from upstream + * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+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 2052576] Re: GCP TDX Support
** Changed in: linux-gcp (Ubuntu Mantic) 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/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+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 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
** Changed in: linux-oracle (Ubuntu Mantic) Status: In Progress => Fix Committed -- 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/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2055473] [NEW] mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
Public bug reported: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Attachment added: "rt.log" https://bugs.launchpad.net/bugs/2055473/+attachment/5750793/+files/rt.log ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) 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/2055473 Title: mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+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 2052576] Re: GCP TDX Support
Google tested packages from build PPA. ** Tags removed: verification-needed-mantic-linux-gcp ** Tags added: verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+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 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
All 64k packages being correctly produced from arm64. ** Tags removed: verification-needed-mantic-linux-oracle ** Tags added: verification-done-mantic-linux-oracle -- 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/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-6.5 package in Ubuntu: Invalid Status in linux-oracle source package in Jammy: Invalid Status in linux-oracle-6.5 source package in Jammy: Fix Committed Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle-6.5 source package in Mantic: Invalid Status in linux-oracle source package in Noble: In Progress Status in linux-oracle-6.5 source package in Noble: Invalid Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+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 2056616] Re: left-over ceph debugging printks
** Also affects: linux (Ubuntu Noble) 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/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+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 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I've tested an initial version with the upstream patch and attached the
debdiff here. Will work to get this uploaded.
** Patch added: "zfs-linux_2.2.2-0ubuntu9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2058179/+attachment/5767995/+files/zfs-linux_2.2.2-0ubuntu9.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Confirmed
Status in systemd source package in Noble:
Triaged
Status in zfs-linux source package in Noble:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
** Changed in: zfs-linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Noble)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
In Progress
Status in systemd source package in Noble:
Triaged
Status in zfs-linux source package in Noble:
In Progress
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2070402] Re: net: mana: Add support for page sizes other than 4KB on ARM64
** Tags removed: verification-needed-jammy-linux-azure verification-needed-noble-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-noble-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2070402 Title: net: mana: Add support for page sizes other than 4KB on ARM64 Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Noble: Fix Committed Status in linux-azure source package in Oracular: Fix Committed Bug description: SRU Justification [Impact] * Request from MSFT to add MANA support for page sizes other than 4KB [Fix] * Clean cherry pick from linux-next, 382d1741b5b2: "net: mana: Add support for page sizes other than 4KB on ARM64" * Uses MANA_PAGE_SIZE, which defaults to 4KB, rather than PAGE_SIZE which is tied to platform page size [Test Plan] * Compile tested * Boot tested * Module loaded [Regression potential] * Changes isolated, minimal regression risk * Functionally equivalent, simply changing the origin of defines [Other info] * SF #00388152 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2070402/+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 2069362] Re: Request to enable VDPA kernel config
** Tags removed: verification-needed-noble-linux-azure ** Tags added: verification-done-noble-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2069362 Title: Request to enable VDPA kernel config Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Noble: Fix Committed Status in linux-azure source package in Oracular: Fix Committed Bug description: SRU Justification [Impact] * Request from MSFT to set the following config options: CONFIG_VDPA=m CONFIG_VDPA_SIM=m CONFIG_VDPA_SIM_NET=m CONFIG_VDPA_SIM_BLOCK=m CONFIG_VHOST_RING=m CONFIG_VHOST_VDPA=m [Fix] * SAUCE patch to enable config options [Test Plan] * Compile tested * Boot tested * Microsoft tested [Regression potential] * Changes isolated, minimal regression risk * Configs enabled in Generic, but missing from Azure [Other info] * SF #00386379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2069362/+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 2071445] Re: Ubuntu 24.04 for Azure unable to run 32bit binaries
** Changed in: linux-azure (Ubuntu Noble) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/2071445 Title: Ubuntu 24.04 for Azure unable to run 32bit binaries Status in linux-azure package in Ubuntu: Triaged Status in linux-signed-azure package in Ubuntu: Invalid Status in linux-signed-azure-6.8 package in Ubuntu: Invalid Status in linux-azure source package in Noble: Fix Committed Bug description: [Impact] ## Issue details The configuration of the kernel in linux-image-6.8.0-1008-azure is incompatible with the way libc6:i386 is built. This leads to the error "The futex facility returned an unexpected error code." and application crash when trying to execute many 32bit applications in x86-64 machines. In very short the issue is the following: This kernel image is compiled with CONFIG_COMPAT_32BIT_TIME=n, unlike the vanilla Ubuntu 24.04 kernel images. But, the glibc / libc6:i386 distributed with Ubuntu24.04 is compiled needing the syscalls enabled with that option. i.e. **This kernel configuration is just incompatible with the provided glibc** In detail: glibc when built for 32bit, if not told which kernel is built for, will decide if the time_t value fits or not in a 32bit time_t, and do either the 32 or 64bit syscall: https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/futex-internal.c;h=0bb1dd51f66802521afd71b9246222ed0ea0d862;hb=refs/heads/release/2.39/master#l90 calls with no deadline fit in the 32bit version, but as the kernel does not provide this syscall, glibc will just get a ENOSYS, and glibc will error out aborting the program ``` abort (abort.c:79) __libc_message_impl.cold (libc_fatal.c:132) __libc_fatal (libc_fatal.c:141) futex_fatal_error (futex-internal.h:87) __futex_abstimed_wait_common (futex-internal.c:119) ``` after printing "The futex facility returned an unexpected error code.\n": https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/nptl/futex-internal.h;h=0e87e92d15ab92f5069463719a494e97d9800431;hb=refs/heads/release/2.39/master#l87 ## Expected behavior: * No crashes for 32bit applications with this kernel * This kernel image built with CONFIG_COMPAT_32BIT_TIME=y ## Aditional info: For reference, this is the current vanilla Ubuntu 24.04 kernel for x86_64 and this config: ``` $ uname -a Linux 6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 15:51:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_COMPAT_32BIT_TIME /boot/config-$(uname -r) CONFIG_COMPAT_32BIT_TIME=y ``` On the other hand this is the kernel config for this kernel image: ``` Linux <> 6.8.0-1008-azure #8-Ubuntu SMP Fri May 17 10:44:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # CONFIG_COMPAT_32BIT_TIME is not set ``` Related github issue (the issue was found in github ubuntu 24.04 runners) https://github.com/actions/runner-images/issues/9977 [Fix] Reenable COMPAT_32BIT_TIME [Test Case] See above. [Where Problems Could Occur] Disabling COMPAT_32BIT_TIME in Noble azure introduced a regression when running x86 binaries, so the fix is not expected to break anything (new). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445/+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 2073414] Re: Include Azure Site Recovery module in Azure kernel
** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Noble) 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/2073414 Title: Include Azure Site Recovery module in Azure kernel Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux source package in Noble: Fix Committed Status in linux-azure source package in Noble: In Progress Status in linux source package in Oracular: New Status in linux-azure source package in Oracular: In Progress Bug description: [Impact] * Microsoft has requested the involflt DKMS module to be included in Azure and Generic kernels [Fix] * For Azure kernels, module will initially be included during kernel build via the dkms-version hooks to provide DKMS modules signed into a kernel build * For Generic kernels (and Azure once complete), the DKMS modules will ultimately be included via a linux-main-modules package, similar to linux-restricted-modules [Test Plan] * Compile and install involflt module * Microsoft tested [Where problems could occur] * Low regression risk, module separate from kernel package and requires separate install [Other info] * SF #00366523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073414/+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 2073414] Re: Include Azure Site Recovery module in Azure kernel
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Noble) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => New ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => New ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => 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/2073414 Title: Include Azure Site Recovery module in Azure kernel Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-azure source package in Focal: Fix Committed Status in linux source package in Jammy: New Status in linux-azure source package in Jammy: Fix Committed Status in linux source package in Noble: New Status in linux-azure source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-azure source package in Oracular: In Progress Bug description: [Impact] * Microsoft has requested the involflt DKMS module to be included in Azure and Generic kernels [Fix] * For Azure kernels, module will initially be included during kernel build via the dkms-version hooks to provide DKMS modules signed into a kernel build * For Generic kernels (and Azure once complete), the DKMS modules will ultimately be included via a linux-main-modules package, similar to linux-restricted-modules [Test Plan] * Compile and install involflt module * Microsoft tested [Where problems could occur] * Low regression risk, module separate from kernel package and requires separate install [Other info] * SF #00366523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073414/+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 2076291] [NEW] kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
Public bug reported:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
[Fix]
* Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables:
Fix null-ptr-deref in iptable_nat_table_init("
[Test Plan]
* Build and boot tested
[Where problems could occur]
* Low regression risk
[Other info]
* SF #00391736
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Summary changed:
- kernel panic was caused by a fatal exception due to a null pointer
dereference in the iptable_nat module Case Team (4) Case Time Cards (5)
Open Activities (0) Activity History (0) Files (0) Case History (10+)
SurveyMonkey Responses (0) Emails (0) Case Status History (5) Case Reviews (0)
Case Comments (0) Notes (0) Tabs Details Contacts Comments
Files Related Knowledge Tracking Assets Account Cases Case
Action Plan and Engineering Notes Action Plan Engineering Notes Post
New Case Time Card Share an update... I've provided a test kernel To link
to a record, enter / then start typing the record name. To Canonical
Ltd. Only Case Case Details Time Spent (Minutes) Solution Sent Tick
Solution Sent Tick Status Waiting on Customer Workaround Sent Tick
Workaround Sent Tick Most Recent Activity All Updates Emails
Private Answers Call Logs Text Posts Status Changes Skip Feed View
This Post Click to collapse post Melissa Carlson Melissa Carlson August 7, 2024
at 1:58 PM Post To: Internal Kernel Escalation Hi John, Azure is
requesting to pull in the following upstream patch to address an issue they're
seeing on AKS:
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
Based on this coming from AKS I would expect we'll want to evaluate
pulling this in for 5.15+ but I've asked Jack to confirm. Let us know if
you see any concerns with pulling this patch in. -Melissa This content is
a preview of a link. patchwork.kernel.org patchwork.kernel.org
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
Comment Click to expand post System System August 7, 2024 at 12:39 PM Case
Case updated View This Post Click to collapse post Melissa Carlson Melissa
Carlson August 7, 2024 at 1:38 PM Post To: All
+ kernel panic was caused by a fatal exception due to a null pointer
dereference in the iptable_nat module
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2076291
Title:
kernel panic was caused by a fatal exception due to a null pointer
dereference in the iptable_nat module
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Jammy:
New
Bug description:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
[Fix]
* Clean cherry-pick upstream commit 5830aa863981: "netfilter:
iptables: Fix null-ptr-deref in iptable_nat_table_init("
[Test Plan]
* Build and boot tested
[Where problems could occur]
* Low regression risk
[Other info]
* SF #00391736
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2073414] Re: Include Azure Site Recovery module in Azure kernel
** Tags removed: verification-needed-focal-linux-azure ** Tags added: verification-done-focal-linux-azure -- 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/2073414 Title: Include Azure Site Recovery module in Azure kernel Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-azure source package in Focal: Fix Committed Status in linux source package in Jammy: New Status in linux-azure source package in Jammy: Fix Committed Status in linux source package in Noble: New Status in linux-azure source package in Noble: Fix Committed Status in linux source package in Oracular: New Status in linux-azure source package in Oracular: In Progress Bug description: [Impact] * Microsoft has requested the involflt DKMS module to be included in Azure and Generic kernels [Fix] * For Azure kernels, module will initially be included during kernel build via the dkms-version hooks to provide DKMS modules signed into a kernel build * For Generic kernels (and Azure once complete), the DKMS modules will ultimately be included via a linux-main-modules package, similar to linux-restricted-modules [Test Plan] * Compile and install involflt module * Microsoft tested [Where problems could occur] * Low regression risk, module separate from kernel package and requires separate install [Other info] * SF #00366523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073414/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
** Description changed:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
+ similar to the upstream issue here -
+
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
[Fix]
* Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables:
- Fix null-ptr-deref in iptable_nat_table_init("
+ Fix null-ptr-deref in iptable_nat_table_init()"
[Test Plan]
* Build and boot tested
[Where problems could occur]
- * Low regression risk
+ * Low regression risk, mostly shifting logic
+ * Change to order of register_pernet_subsys() and xt_register_template()
could expose some other logic being held together under race condition
[Other info]
* SF #00391736
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2076291
Title:
kernel panic was caused by a fatal exception due to a null pointer
dereference in the iptable_nat module
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Jammy:
New
Bug description:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
similar to the upstream issue here -
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
[Fix]
* Clean cherry-pick upstream commit 5830aa863981: "netfilter:
iptables: Fix null-ptr-deref in iptable_nat_table_init()"
[Test Plan]
* Build and boot tested
[Where problems could occur]
* Low regression risk, mostly shifting logic
* Change to order of register_pernet_subsys() and xt_register_template()
could expose some other logic being held together under race condition
[Other info]
* SF #00391736
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
** Changed in: linux-azure (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2076291 Title: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Committed Bug description: [Impact] * Microsoft has requested a patch to address a kernel panic issue similar to the upstream issue here - https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/ [Fix] * Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init()" [Test Plan] * Build and boot tested [Where problems could occur] * Low regression risk, mostly shifting logic * Change to order of register_pernet_subsys() and xt_register_template() could expose some other logic being held together under race condition [Other info] * SF #00391736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
** Also affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Oracular) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2076291 Title: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Noble: Fix Committed Status in linux-azure source package in Oracular: Fix Committed Bug description: [Impact] * Microsoft has requested a patch to address a kernel panic issue similar to the upstream issue here - https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/ [Fix] * Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init()" [Test Plan] * Build and boot tested [Where problems could occur] * Low regression risk, mostly shifting logic * Change to order of register_pernet_subsys() and xt_register_template() could expose some other logic being held together under race condition [Other info] * SF #00391736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2077991] [NEW] Provide an arm64 linux-azure 64k kernel variant
Public bug reported: [Impact] * Microsoft requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00388238 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2077991 Title: Provide an arm64 linux-azure 64k kernel variant Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: New Status in linux-azure source package in Noble: New Status in linux-azure source package in Oracular: New Bug description: [Impact] * Microsoft requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00388238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2077991/+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 2077991] Re: Provide an arm64 linux-azure 64k kernel variant
** Description changed: [Impact] * Microsoft requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] - * Low chance of regression. Isolated logic fix. + * Low chance of regression as no logic changed. + * Simply adding a new flavour, easily verified by checking built packages. [Other Info] * SF #00388238 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2077991 Title: Provide an arm64 linux-azure 64k kernel variant Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: New Status in linux-azure source package in Noble: New Status in linux-azure source package in Oracular: New Bug description: [Impact] * Microsoft requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression as no logic changed. * Simply adding a new flavour, easily verified by checking built packages. [Other Info] * SF #00388238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2077991/+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 2071445] Re: Ubuntu 24.04 for Azure unable to run 32bit binaries
** Also affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: Triaged ** Also affects: linux-signed-azure (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Also affects: linux-signed-azure-6.8 (Ubuntu Oracular) Importance: Undecided Status: Invalid ** Changed in: linux-azure (Ubuntu Oracular) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/2071445 Title: Ubuntu 24.04 for Azure unable to run 32bit binaries Status in linux-azure package in Ubuntu: Fix Committed Status in linux-signed-azure package in Ubuntu: Invalid Status in linux-signed-azure-6.8 package in Ubuntu: Invalid Status in linux-azure source package in Noble: Fix Released Status in linux-azure source package in Oracular: Fix Committed Status in linux-signed-azure source package in Oracular: Invalid Status in linux-signed-azure-6.8 source package in Oracular: Invalid Bug description: [Impact] ## Issue details The configuration of the kernel in linux-image-6.8.0-1008-azure is incompatible with the way libc6:i386 is built. This leads to the error "The futex facility returned an unexpected error code." and application crash when trying to execute many 32bit applications in x86-64 machines. In very short the issue is the following: This kernel image is compiled with CONFIG_COMPAT_32BIT_TIME=n, unlike the vanilla Ubuntu 24.04 kernel images. But, the glibc / libc6:i386 distributed with Ubuntu24.04 is compiled needing the syscalls enabled with that option. i.e. **This kernel configuration is just incompatible with the provided glibc** In detail: glibc when built for 32bit, if not told which kernel is built for, will decide if the time_t value fits or not in a 32bit time_t, and do either the 32 or 64bit syscall: https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/futex-internal.c;h=0bb1dd51f66802521afd71b9246222ed0ea0d862;hb=refs/heads/release/2.39/master#l90 calls with no deadline fit in the 32bit version, but as the kernel does not provide this syscall, glibc will just get a ENOSYS, and glibc will error out aborting the program ``` abort (abort.c:79) __libc_message_impl.cold (libc_fatal.c:132) __libc_fatal (libc_fatal.c:141) futex_fatal_error (futex-internal.h:87) __futex_abstimed_wait_common (futex-internal.c:119) ``` after printing "The futex facility returned an unexpected error code.\n": https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/nptl/futex-internal.h;h=0e87e92d15ab92f5069463719a494e97d9800431;hb=refs/heads/release/2.39/master#l87 ## Expected behavior: * No crashes for 32bit applications with this kernel * This kernel image built with CONFIG_COMPAT_32BIT_TIME=y ## Aditional info: For reference, this is the current vanilla Ubuntu 24.04 kernel for x86_64 and this config: ``` $ uname -a Linux 6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 15:51:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_COMPAT_32BIT_TIME /boot/config-$(uname -r) CONFIG_COMPAT_32BIT_TIME=y ``` On the other hand this is the kernel config for this kernel image: ``` Linux <> 6.8.0-1008-azure #8-Ubuntu SMP Fri May 17 10:44:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux # CONFIG_COMPAT_32BIT_TIME is not set ``` Related github issue (the issue was found in github ubuntu 24.04 runners) https://github.com/actions/runner-images/issues/9977 [Fix] Reenable COMPAT_32BIT_TIME [Test Case] See above. [Where Problems Could Occur] Disabling COMPAT_32BIT_TIME in Noble azure introduced a regression when running x86 binaries, so the fix is not expected to break anything (new). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445/+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 2078001] Re: Backport "net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response"
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-azure (Ubuntu Oracular)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2078001
Title:
Backport "net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc
response"
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-azure source package in Noble:
Fix Committed
Status in linux-azure source package in Oracular:
Fix Committed
Bug description:
[Impact]
Microsoft has requested us to backport the following bugfix, currently
in the netdev tree:
8af174ea863c net: mana: Fix race of mana_hwc_post_rx_wqe and new hwc response
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8af174ea863c72f25ce31cee3baad8a301c0cf0f
[Fix]
Clean cherry-pick from the netdev tree to the
{oracular,noble,jammy}:linux-azure trees.
[Test plan]
Build and boot tested.
[Where problems could occur]
This seems to have a low risk of regression, since it's just making
sure to finish posting an RX workqueue event before waiting for
completion in order to avoid a race condition with the hardware.
However, any regressions here would likely impact users as MANA-
related errors/timeouts.
[Other info]
SF #00393766
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2078001/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
Fix verified by Microsoft and included in this release. ** Tags removed: verification-needed-jammy-linux-azure verification-needed-noble-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-noble-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2076291 Title: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Noble: Fix Committed Status in linux-azure source package in Oracular: Fix Committed Bug description: [Impact] * Microsoft has requested a patch to address a kernel panic issue similar to the upstream issue here - https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/ [Fix] * Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init()" [Test Plan] * Build and boot tested [Where problems could occur] * Low regression risk, mostly shifting logic * Change to order of register_pernet_subsys() and xt_register_template() could expose some other logic being held together under race condition [Other info] * SF #00391736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
Updating LP bug to SRU justification format. ** Description changed: - 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), + [Impact] + + * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. + + [Fix] + + * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime + update" from upstream ZFS as quilt patch. + + [Test Case] + + * Build tested against Noble generic + * Ran autopkgktests for regressions, none encountered + + [Where things could go wrong] + + * Low chance of regression, isolated instantiation and logic fix. + * Addition of time delta check could cause issues during unexpected delay > 2 seconds. -- 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/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: In Progress Bug description: [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2079841] [NEW] Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM"
Public bug reported: SRU Justification [Impact] * LP #2069204 disabled CET Shadow Stack on SEV-SNP due to CPUID emulation bug not being fixed in VMs until October 2024. * This issue is now fixed, so the patch can be reverted. [Fix] * Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on SEV- SNP due to a paravisor bug" [Test Plan] * Compile tested * Boot tested * Microsoft tested [Regression potential] * Reverting back to previous state, so regression very unlikely. * Changes isolated, minimal regression risk [Other info] * SF #00387447 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2079841 Title: Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM" Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Noble: New Status in linux-azure source package in Oracular: New Bug description: SRU Justification [Impact] * LP #2069204 disabled CET Shadow Stack on SEV-SNP due to CPUID emulation bug not being fixed in VMs until October 2024. * This issue is now fixed, so the patch can be reverted. [Fix] * Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on SEV-SNP due to a paravisor bug" [Test Plan] * Compile tested * Boot tested * Microsoft tested [Regression potential] * Reverting back to previous state, so regression very unlikely. * Changes isolated, minimal regression risk [Other info] * SF #00387447 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2079841/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
** Description changed: + SRU Justification + [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. -- 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/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: In Progress Bug description: SRU Justification [Impact] * 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. [Fix] * Include f0bf7a247dbb: "[PATCH] Linux 6.7 compat: zfs_setattr fix atime update" from upstream ZFS as quilt patch. [Test Case] * Build tested against Noble generic * Ran autopkgktests for regressions, none encountered [Where things could go wrong] * Low chance of regression, isolated instantiation and logic fix. * Addition of time delta check could cause issues during unexpected delay > 2 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2079841] Re: Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM"
** Description changed: SRU Justification [Impact] * LP #2069204 disabled CET Shadow Stack on SEV-SNP due to CPUID emulation bug not being fixed in VMs until October 2024. * This issue is now fixed, so the patch can be reverted. [Fix] * Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on SEV- SNP due to a paravisor bug" [Test Plan] * Compile tested * Boot tested - * Microsoft tested [Regression potential] * Reverting back to previous state, so regression very unlikely. * Changes isolated, minimal regression risk [Other info] * SF #00387447 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2079841 Title: Revert fix for "Kernel fails to enable XSAVE when running in a “v5” AMD SEV-SNP VM" Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Noble: New Status in linux-azure source package in Oracular: New Bug description: SRU Justification [Impact] * LP #2069204 disabled CET Shadow Stack on SEV-SNP due to CPUID emulation bug not being fixed in VMs until October 2024. * This issue is now fixed, so the patch can be reverted. [Fix] * Revert "UBUNTU: SAUCE: x86/hyperv: temporarily disable CET SS on SEV-SNP due to a paravisor bug" [Test Plan] * Compile tested * Boot tested [Regression potential] * Reverting back to previous state, so regression very unlikely. * Changes isolated, minimal regression risk [Other info] * SF #00387447 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2079841/+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 1996093] Re: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996093 Title: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154 Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-azure source package in Focal: Invalid Status in linux-azure-4.15 source package in Focal: Invalid Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996093/+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 1995408] [NEW] [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
Public bug reported: Running fio on NVME SSD can cause CPU soft locks. ** 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/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux package in Ubuntu: New Bug description: Running fio on NVME SSD can cause CPU soft locks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+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 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+attachment/5628321/+files/820e9193-4187-4828-a77b-65cd1bb6ab7e.serialconsole.txt -- 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/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux package in Ubuntu: Incomplete Bug description: Running fio on NVME SSD can cause CPU soft locks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+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 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Description changed: - Running fio on NVME SSD can cause CPU soft locks. + SRU Justification + + [Impact] + + Hypervisor only allocates interrupts to happen on a single physical GPU, + which can lead to CPU soft locks when using PCI NVME under heavy load. + + Kinetic will get this patch via stable updates. + + [Test Case] + + Microsoft tested + + [Where things could go wrong] + + Hypervisor PCI driver may not load correctly. Patch did not apply + cleanly and could lead to merge conflicts once the upstream patch is + pulled in. + + [Other Info] + + SF: #00346549 -- 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/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995408/+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 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux-azure package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1995408/+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 1995408] Re: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks
** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1995408 Title: [Azure] [NVMe] cpu soft lockup issue when run fio against nvme disks Status in linux-azure package in Ubuntu: Incomplete Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00346549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1995408/+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 1996093] [NEW] [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154
Public bug reported: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Attachment added: "KernelLogStatus[1].txt" https://bugs.launchpad.net/bugs/1996093/+attachment/5630096/+files/KernelLogStatus%5B1%5D.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1996093 Title: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154 Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996093/+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
** Also affects: linux-gkeop (Ubuntu) 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gkeop package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux-gkeop source package in Jammy: New Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released 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/+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 2039191] [NEW] Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Public bug reported: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** 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 Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Jammy: New Status in linux-gcp source package in Jammy: New Status in linux-aws source package in Lunar: New Status in linux-gcp source package in Lunar: New Status in linux-aws source package in Mantic: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Triaged -- 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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Triaged Status in linux-aws source package in Jammy: Triaged Status in linux-gcp source package in Jammy: Triaged Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Triaged Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Triaged Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Removing Jammy from nominations as jammy:linux-gcp-6.2 and jammy:linux- aws-6.2 will be getting the patch via lunar:linux-gcp and lunar:linux- aws respectively. ** No longer affects: linux-gcp (Ubuntu Jammy) ** No longer affects: linux-aws (Ubuntu Jammy) -- 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/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Triaged Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Triaged Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Triaged Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2037087] Re: TCPDirect patches
** Changed in: linux-gcp-5.15 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2037087
Title:
TCPDirect patches
Status in linux-gcp-5.15 package in Ubuntu:
New
Status in linux-gcp-5.15 source package in Focal:
Fix Committed
Bug description:
[Impact]
* Include patches to enable TCPDirect. This is considered a v1 implementation
while Google works to
upsteam a v2 implementation, hence the "UBUNTU: SAUCE: (no-up)"
classification.
[Fix]
d1016eee0b1a ("UBUNTU: SAUCE: (no-up) UPSTREAM: tcp: derive delack_max from
rto_min")
10364f0d83ee ("UBUNTU: SAUCE: (no-up) gve: Add retry logic for recoverable
adminq errors")
403fb6f43a7c ("UBUNTU: SAUCE: (no-up) tcp: defer regular ACK while processing
socket backlog")
be97d51d24da ("UBUNTU: SAUCE: (no-up) gve: Enable header-split without
gve_close/gve_open")
499a0ec31c74 ("UBUNTU: SAUCE: (no-up) gve: fix rx issues for skb free and
append frags")
89b4d1e69fac ("UBUNTU: SAUCE: (no-up) net: fix silent put_cmsg() failures")
d025ece61dab ("UBUNTU: SAUCE: (no-up) tcp: get rid of
sysctl_tcp_adv_win_scale")
d1380ff2f4e3 ("UBUNTU: SAUCE: (no-up) gve: Add tx watchdog to avoid race
condition on miss path")
a4bc2e0cd1a3 ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for
active flows")
bbe85e8e856c ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for
4K MTU TCP flows")
7d5f15f733e8 ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow")
22668842a913 ("UBUNTU: SAUCE: (no-up) gve: add flow steering and rss reset
when teardown device resources")
18e66e5d9ac4 ("UBUNTU: SAUCE: (no-up) net: create skb_frags_not_readable()
helper")
5d81162de488 ("UBUNTU: SAUCE: (no-up) net: add missing skb->devmem checks")
cf0bcfdf9f87 ("UBUNTU: SAUCE: (no-up) net: remove devmem check from
__pskb_copy_fclone()")
9ca03b5c36c7 ("UBUNTU: SAUCE: (no-up) net: allow tcp coallapsing and
coallescing for devmem skbs")
030aef8b0fd2 ("UBUNTU: SAUCE: (no-up) net: skb_store_bits() should succeed on
devmem header")
6aaf939fb49e ("UBUNTU: SAUCE: (no-up) net: fix skb_split unnecessarily
setting skb->devmem")
51e12a8201a1 ("UBUNTU: SAUCE: (no-up) net: skb_copy_bits() should be able to
copy devmem header")
ea8a78e040f5 ("UBUNTU: SAUCE: (no-up) net: fix memory leaks due to
skb->devmem checks")
1fcd891606c0 ("UBUNTU: SAUCE: (no-up) net: fix snaplen for devmem packets")
e4a4e05f4831 ("UBUNTU: SAUCE: (no-up) net: keep track and avoid access of skb
containing dma-buf pages.")
424871c3c564 ("UBUNTU: SAUCE: (no-up) gve: implement device memory socket
data path")
4f8668ee4cdb ("UBUNTU: SAUCE: (no-up) gve: implement devmem socket stats")
abe1772b0e39 ("UBUNTU: SAUCE: (no-up) gve: add rss support")
c08a1adb6130 ("UBUNTU: SAUCE: (no-up) gve: add flow steering support")
ffa842923ad6 ("UBUNTU: SAUCE: (no-up) gve: Add header split support")
940527385c4c ("UBUNTU: SAUCE: (no-up) lakitu config: enable TCP Direct
configs")
ebfa162318f8 ("UBUNTU: SAUCE: (no-up) tcp, cos-only: revert changes to
skb_zerocopy_iter_stream")
b87d0b0e659a ("UBUNTU: SAUCE: (no-up) tcp: let sendmsg() take file
descriptors via cmsg to enable devmem Tx")
1d523c425a8c ("UBUNTU: SAUCE: (no-up) net: add SO_DEVMEM_DONTNEED setsockopt
to release pages")
3e34b0936884 ("UBUNTU: SAUCE: (no-up) net: backport fixes to devmem TCP rx")
446d7a742177 ("UBUNTU: SAUCE: (no-up) tcp: implement RX path for devmem
sockets")
109f2e3feb98 ("UBUNTU: SAUCE: (no-up) net: use get_file_rcu() instead of
get_file for __netdev_rxq_alloc_page_from_dmabuf_pool")
0d5117d4ea53 ("UBUNTU: SAUCE: (no-up) net: add netdev_rxq_alloc_page and
skb->devmem")
d0d273544148 ("UBUNTU: SAUCE: (no-up) dmabuf: add ioctl that binds dmabuf
pagepool to a netdevice")
05c81288f77b ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow in addr
calculation")
46366a3326d9 ("UBUNTU: SAUCE: (no-up) dma-buf: create struct pages backing a
dma-bu")
[Test Case]
* Compile tested
* Boot tested
* Ran ubuntu_kernel_selftests and ubuntu_performance_stress_ng test suites
* Tested by Google
[Other Info]
* Bulk of patchset came from
https://cos.googlesource.com/third_party/kernel/+log/refs/heads/tcpd/R105,
but some backports were given in SalesForce case below.
* SF: #00359122
[Where things could go wrong]
* Most changes target Google gve driver specifically.
* Some required updates to dma and network implementation to enable new API.
* Could lead to DMA or network instabilities
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp-5.15/+bug/2037087/+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.launchpa
[Kernel-packages] [Bug 2039720] [NEW] Intel IDPF support
Public bug reported: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google ** 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 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/2039720 Title: Intel IDPF support 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: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2039732] [NEW] No graphic desktop environment on Google GCP instances
Public bug reported: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. ** 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/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: New Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2039732] Re: No graphic desktop environment on Google GCP instances
** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** 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/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: 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: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2039720] Re: Intel IDPF support
** Description changed: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google + + [Other Info] + + * SF #00368902 -- 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/2039720 Title: Intel IDPF support 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: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2039732] Re: No graphic desktop environment on Google GCP instances
** Description changed: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. + + [Other Info] + + * SF #00366439 -- 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/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: 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: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
Tested the kernel from lunar proposed (6.2.0-1018-gcp) on GCP n2d instances. The image boots with sev enabled: john_cabaj@john-cabaj-sev-snp2:~$ sudo dmesg | grep -i sev [0.303257] Memory Encryption Features active: AMD SEV ** Tags removed: verification-needed-lunar-linux-gcp ** Tags added: verification-done-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
** 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 ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Lunar) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: 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: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
** Changed in: linux-gcp (Ubuntu Mantic) Status: Triaged => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2039732] Re: No graphic desktop environment on Google GCP instances
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) 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/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2028740] Re: Fix AMD gpu hang when screen off/on
This is still seen on generic jammy:hwe-6.2. Log attached was from machine still up, just with display off. ** Attachment added: "sleep.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028740/+attachment/5713061/+files/sleep.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2028740 Title: Fix AMD gpu hang when screen off/on Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] AMD GPU hang when screen off/on. error log: kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 [Fix] Keep a PHY active when detecting DP signal + DPMS active. [Test] Tested on 3 AMD platforms, GPU works fine. [Where problems could occur] Low risk, the fix is in v6.4-rc1. Generic Jammy kernel doesn't need this commit because of no support of AMD Phoenix GPU. SRU for Lunar/oem-6.1 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028740/+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 2040337] [NEW] Incorrect argument from SEV live-migration fix
Public bug reported: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: High Assignee: John Cabaj (john-cabaj) Status: In Progress ** Affects: linux-gcp (Ubuntu Jammy) Importance: High Assignee: John Cabaj (john-cabaj) Status: In Progress ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** 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 Focal) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Focal) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: In Progress Status in linux-gcp source package in Jammy: In Progress Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2040337] Re: Incorrect argument from SEV live-migration fix
** Description changed: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] - * Upstream ac3f9c9f1b37 introduced change to - notify_range_enc_status_changed() to accept page size instead of number - of pages, but function was not updated. Updating to send correct - argument. + * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX + support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 -- 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/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: In Progress Status in linux-gcp source package in Jammy: In Progress Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2040522] [NEW] gVNIC DQO-QPL feature
Public bug reported: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 ** 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 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 ** Also affects: linux-gcp (Ubuntu Mantic) 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/2040522 Title: gVNIC DQO-QPL feature 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: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Verified to boot successfully. 32-bit machines otherwise not used on GCP, anyway. ** Tags removed: verification-needed-mantic-linux-gcp ** Tags added: verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2040337] Re: Incorrect argument from SEV live-migration fix
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) 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/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2003374] Re: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols
Adding Jammy package to affected so UBSAN can be re-enabled once kpatch is patched. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Kinetic) -- 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/2003374 Title: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols Status in dh-kpatches: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in kpatch package in Ubuntu: In Progress Status in linux package in Ubuntu: New Status in kpatch source package in Jammy: In Progress Status in linux source package in Jammy: New Status in kpatch source package in Kinetic: New Bug description: [ Impact ] * When UBSAN is enabled in an s390x kernel configuration, kpatch- build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log). * Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality. [ Test Plan ] * Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful. [ Where problems could occur ] * A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. To manage notifications about this bug go to: https://bugs.launchpad.net/dh-kpatches/+bug/2003374/+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 1639924] Re: Kernel livepatch support for for s390x
Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). Patch submitted and tested - pending mailing list review. ** Bug watch added: github.com/SUSE/qa_test_klp/issues #17 https://github.com/SUSE/qa_test_klp/issues/17 -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Committed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-obj
[Kernel-packages] [Bug 2013603] [NEW] Kernel livepatch ftrace graph fix
Public bug reported: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => 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/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+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 2015097] [NEW] Kernel crash during Mellanox performance testing
Public bug reported: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+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 2015097] Re: Kernel crash during Mellanox performance testing
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Description changed: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test - * IBM performance test + * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic -- 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+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 2013603] Re: Kernel livepatch ftrace graph fix
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+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
** Changed in: linux-gcp (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) 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-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: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed 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 2034894] Re: Fix requested for SEV live-migration
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: 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 2037087] [NEW] TCPDirect patches
Public bug reported:
[Impact]
* Include patches to enable TCPDirect. This is considered a v1 implementation
while Google works to
upsteam a v2 implementation, hence the "UBUNTU: SAUCE: (no-up)"
classification.
[Fix]
d1016eee0b1a ("UBUNTU: SAUCE: (no-up) UPSTREAM: tcp: derive delack_max from
rto_min")
10364f0d83ee ("UBUNTU: SAUCE: (no-up) gve: Add retry logic for recoverable
adminq errors")
403fb6f43a7c ("UBUNTU: SAUCE: (no-up) tcp: defer regular ACK while processing
socket backlog")
be97d51d24da ("UBUNTU: SAUCE: (no-up) gve: Enable header-split without
gve_close/gve_open")
499a0ec31c74 ("UBUNTU: SAUCE: (no-up) gve: fix rx issues for skb free and
append frags")
89b4d1e69fac ("UBUNTU: SAUCE: (no-up) net: fix silent put_cmsg() failures")
d025ece61dab ("UBUNTU: SAUCE: (no-up) tcp: get rid of sysctl_tcp_adv_win_scale")
d1380ff2f4e3 ("UBUNTU: SAUCE: (no-up) gve: Add tx watchdog to avoid race
condition on miss path")
a4bc2e0cd1a3 ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for
active flows")
bbe85e8e856c ("UBUNTU: SAUCE: (no-up) net-tcp_5k_mtu: force wscale >= 12 for 4K
MTU TCP flows")
7d5f15f733e8 ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow")
22668842a913 ("UBUNTU: SAUCE: (no-up) gve: add flow steering and rss reset when
teardown device resources")
18e66e5d9ac4 ("UBUNTU: SAUCE: (no-up) net: create skb_frags_not_readable()
helper")
5d81162de488 ("UBUNTU: SAUCE: (no-up) net: add missing skb->devmem checks")
cf0bcfdf9f87 ("UBUNTU: SAUCE: (no-up) net: remove devmem check from
__pskb_copy_fclone()")
9ca03b5c36c7 ("UBUNTU: SAUCE: (no-up) net: allow tcp coallapsing and
coallescing for devmem skbs")
030aef8b0fd2 ("UBUNTU: SAUCE: (no-up) net: skb_store_bits() should succeed on
devmem header")
6aaf939fb49e ("UBUNTU: SAUCE: (no-up) net: fix skb_split unnecessarily setting
skb->devmem")
51e12a8201a1 ("UBUNTU: SAUCE: (no-up) net: skb_copy_bits() should be able to
copy devmem header")
ea8a78e040f5 ("UBUNTU: SAUCE: (no-up) net: fix memory leaks due to skb->devmem
checks")
1fcd891606c0 ("UBUNTU: SAUCE: (no-up) net: fix snaplen for devmem packets")
e4a4e05f4831 ("UBUNTU: SAUCE: (no-up) net: keep track and avoid access of skb
containing dma-buf pages.")
424871c3c564 ("UBUNTU: SAUCE: (no-up) gve: implement device memory socket data
path")
4f8668ee4cdb ("UBUNTU: SAUCE: (no-up) gve: implement devmem socket stats")
abe1772b0e39 ("UBUNTU: SAUCE: (no-up) gve: add rss support")
c08a1adb6130 ("UBUNTU: SAUCE: (no-up) gve: add flow steering support")
ffa842923ad6 ("UBUNTU: SAUCE: (no-up) gve: Add header split support")
940527385c4c ("UBUNTU: SAUCE: (no-up) lakitu config: enable TCP Direct configs")
ebfa162318f8 ("UBUNTU: SAUCE: (no-up) tcp, cos-only: revert changes to
skb_zerocopy_iter_stream")
b87d0b0e659a ("UBUNTU: SAUCE: (no-up) tcp: let sendmsg() take file descriptors
via cmsg to enable devmem Tx")
1d523c425a8c ("UBUNTU: SAUCE: (no-up) net: add SO_DEVMEM_DONTNEED setsockopt to
release pages")
3e34b0936884 ("UBUNTU: SAUCE: (no-up) net: backport fixes to devmem TCP rx")
446d7a742177 ("UBUNTU: SAUCE: (no-up) tcp: implement RX path for devmem
sockets")
109f2e3feb98 ("UBUNTU: SAUCE: (no-up) net: use get_file_rcu() instead of
get_file for __netdev_rxq_alloc_page_from_dmabuf_pool")
0d5117d4ea53 ("UBUNTU: SAUCE: (no-up) net: add netdev_rxq_alloc_page and
skb->devmem")
d0d273544148 ("UBUNTU: SAUCE: (no-up) dmabuf: add ioctl that binds dmabuf
pagepool to a netdevice")
05c81288f77b ("UBUNTU: SAUCE: (no-up) dma-buf: fix int overflow in addr
calculation")
46366a3326d9 ("UBUNTU: SAUCE: (no-up) dma-buf: create struct pages backing a
dma-bu")
[Test Case]
* Compile tested
* Boot tested
* Ran ubuntu_kernel_selftests and ubuntu_performance_stress_ng test suites
* Tested by Google
[Other Info]
* Bulk of patchset came from
https://cos.googlesource.com/third_party/kernel/+log/refs/heads/tcpd/R105,
but some backports were given in SalesForce case below.
* SF: #00359122
[Where things could go wrong]
* Most changes target Google gve driver specifically.
* Some required updates to dma and network implementation to enable new API.
* Could lead to DMA or network instabilities
** Affects: linux-gcp-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-gcp-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-gcp-5.15 (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-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2037087
Title:
TCPDirect patches
Status in linux-gcp-5.15 package in Ubuntu:
New
Status in linux-gcp-5.15 source package in Focal:
New
Bug description:
[Impact]
* Include patches to enable TCPDirect. This is considered a v1 implementation
while Google works to
upsteam a v2 implementation, hence the "UBUNTU: SAUCE: (no-up)"
classification.
[Fix]
d1016eee0b1a ("UBUNTU: SAUCE:
[Kernel-packages] [Bug 2037316] [NEW] SEV_SNP failure to init
Public bug reported: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. ** Affects: linux-gcp (Ubuntu) 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 Lunar) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) 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/2037316 Title: SEV_SNP failure to init Status in linux-gcp package in Ubuntu: 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: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2037316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
Patches submitted to mantic:linux-gcp and lunar:linux-gcp for 2023.10.02 SRU cycle. jammy:linux-gcp-6.2 will get changes from lunar:linux-gcp during aforementioned SRU cycle. ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2037316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
Fix was tested by Google, and the relevant patch is in all releases of linux-gcp and linux-gke affected. ** Changed in: linux-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => Fix Released ** Changed in: linux-gke (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released 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/+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 2034894] Re: Fix requested for SEV live-migration
Fix was tested by Google, and the relevant patch is in all releases of linux-gcp affected. ** Changed in: linux-gcp (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: linux-gcp (Ubuntu Mantic) 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/2034894 Title: Fix requested for SEV live-migration Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released 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 2015097] Re: Kernel crash during Mellanox performance testing
Tested with 5.15.0-72.79: [ Test Case ] * Boot testing passed * IBM tested functionality indirectly through derivative IBM kernel that got same patch ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) * Change landed v5.19 upstream, Kinetic onward not affected [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+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 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Description changed: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] - * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. + * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 ** Description changed: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] - * All cherry-picks from upstream + * Mantic: all clean cherry-picks from upstream + * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 -- 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/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2039720] Re: Intel IDPF support
** No longer affects: linux-gcp (Ubuntu Focal) ** 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/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2039720] Re: Intel IDPF support
** Description changed: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] - * Cherry pick commits from net-next, - b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 + * Mantic - 24 clean cherry-picks, 1 backport from upstream + * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested - * To be tested by Google + * Tested internally and by Google using neper (https://github.com/google/neper) + * Networking is functional and throughput is as expected [Where things could go wrong] - * Low chance of regression, new driver is isolated and will be tested by - Google + * Low chance of regression, changes have been upstream since 6.6 kernel + * Bulk of changes in IDPF driver + * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 -- 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/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2039720] Re: Intel IDPF support
** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2049922] [NEW] PCI ATS quirk patch needed for IDPF
Public bug reported: [Impact] * Request from Google to include Intel patches for IDPF support if used from out-of-tree module to prevent system instability [Fix] * Upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7&id=a18615b1cfc04f00548c60eb9a77e0ce56e848fd [Test Case] * Compile test * Boot test * Test on non-IDPF instance [Where things could go wrong] * Low chance of regression, changes very isolated [Other Info] * SF #00376470 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) 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/2049922 Title: PCI ATS quirk patch needed for IDPF 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 Bug description: [Impact] * Request from Google to include Intel patches for IDPF support if used from out-of-tree module to prevent system instability [Fix] * Upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7&id=a18615b1cfc04f00548c60eb9a77e0ce56e848fd [Test Case] * Compile test * Boot test * Test on non-IDPF instance [Where things could go wrong] * Low chance of regression, changes very isolated [Other Info] * SF #00376470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) 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/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2039720] Re: Intel IDPF support
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) 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/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Jammy) Status: In Progress => Fix Released -- 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/2046184 Title: [arm64] Increase max CPU count to 512 Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Jammy: Fix Released Status in linux-oracle source package in Mantic: Fix Released Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2046184/+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 2040522] Re: gVNIC DQO-QPL feature
Verified by Google as part of SF#00366697. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+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 2039720] Re: Intel IDPF support
Verified by Google as part of SF#00368902 as well as internally on GCE instance. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
I'm currently bisecting the releases and kernels, using releases between 5.4 and 5.15 on an LXD VM. Releases 5.4 through 5.13 exhibit similar speeds, with 5.15 showing a drop-off. The numbers aren't quite the same as above, but that's likely due to setup: 5.4: 744MiB/s average 5.11: 785MiB/s average 5.13: 711MiB/s average 5.15: 602MiB/s average -- 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/2042564 Title: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: We in the Canonical Public Cloud team have received report from our colleagues in Google regarding a potential performance regression with the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were performed using the linux-gkeop and linux-gkeop-5.15 kernels. I have verified with the generic Ubuntu 20.04 5.4 linux-generic and the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels. The tests were run using `fio` fio commands: * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the results are below: Using 5.4 kernel ``` ubuntu@cloudimg:~$ uname --kernel-release 5.4.0-164-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov 2 09:15:22 2023 write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61 clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38 lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80 clat percentiles (usec): | 1.00th=[ 775], 5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024], | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261], | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932], | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676], | 99.99th=[32113] bw ( MiB/s): min= 524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, samples=4232 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, samples=4232 lat (nsec) : 500=0.01%, 750=0.01%, 1000=0.01% lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01% lat (usec) : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93% lat (msec) : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07% lat (msec) : 100=0.01% cpu : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103 IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1% issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=128 Run status group 0 (all jobs): WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), io=320GiB (344GB), run=264837-264837msec Disk stats (read/write): sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, util=100.00% ``` After upgrading to linux-generic-hwe-20.04 kernel and rebooting ``` ubuntu@cloudimg:~$ uname --kernel-release 5.15.0-88-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s] fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov 2 09:46:49 2023 write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50 clat (nsec): min=1100, max=782743k, avg=6595008.67, stdev=6290570.04 lat
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
Verified all configuration changes are in latest release. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-lunar-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-lunar-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next&id=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+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 2040337] Re: Incorrect argument from SEV live-migration fix
Verified requisite change is in focal and jammy releases. Full suite of boot test and regression tests will suffice for verification. ** Tags removed: verification-needed-focal-linux-gcp verification-needed-jammy-linux-gcp ** Tags added: verification-done-focal-linux-gcp verification-done-jammy-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040337 Title: Incorrect argument from SEV live-migration fix Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_range_enc_status_changed() passing incorrect argument. [Fix] * Upstream ac3f9c9f1b37 introduced change to notify_range_enc_status_changed() to accept page size instead of number of pages, but function was not updated. Updating to send correct argument. Upstream implementation changed with TDX support, and is unaffected, so no plans to upstream. [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00367134 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040337/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Verified to boot successfully. 32-bit machines otherwise not used on GCP, anyway. ** Tags removed: verification-needed-lunar-linux-gcp ** Tags added: verification-done-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2044192] [NEW] Patches needed for AmpereOne (arm64)
Public bug reported:
[Impact]
* Google requested patches for AmpereOne machine t ype
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy 5.15
and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL
programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL
programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the
core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer programming
over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from erratum
function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for unhandled
register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Changes isolated to to timers.
[Other Info]
* SF #00372821
** 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 Focal)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
[Impact]
* Google requested patches for AmpereOne machine t ype
[Fix]
+ * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Changes isolated to to timers.
[Other Info]
* SF #00372821
--
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/2044192
Title:
Patches needed for AmpereOne (arm64)
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:
[Impact]
* Google requested patches for AmpereOne machine t ype
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_
[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)
** Description changed:
[Impact]
- * Google requested patches for AmpereOne machine t ype
+ * Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Changes isolated to to timers.
[Other Info]
* SF #00372821
** Description changed:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
- * Low chance of regression. Changes isolated to to timers.
+ * Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
--
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/2044192
Title:
Patches needed for AmpereOne (arm64)
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:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer t
[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Focal)
** Changed in: linux-gcp (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-gcp (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
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/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-gcp source package in Jammy:
Fix Committed
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2044192] Re: Patches needed for AmpereOne (arm64)
** Description changed:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
- * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
+ * Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
+ * Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
- 0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
- * Boot tested
- * To be tested by Google
+ * Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
--
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/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-gcp source package in Jammy:
Fix Committed
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+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 2046184] [NEW] [arm64] Increase max CPU count to 512
Public bug reported: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Description changed: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] - * Update CONFIG_NR_CPUS from 256 to 512 + * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as its compressed. * SF #00366439 ** Description changed: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as its compressed. - * SF #00366439 + * SF #00375112 ** Description changed: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] - * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as its compressed. + * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 -- 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/2046184 Title: [arm64] Increase max CPU count to 512 Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Mantic: New Status in linux-oracle source package in Noble: New Bug description: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2046184/+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 2046184] Re: [arm64] Increase max CPU count to 512
Lunar will be EOL and Jammy now has the 6.5 kernel, so not including Lunar. ** Also affects: linux-oracle (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Noble) 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/2046184 Title: [arm64] Increase max CPU count to 512 Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Jammy: In Progress Status in linux-oracle source package in Mantic: In Progress Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2046184/+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 2076291] Re: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module
** Tags removed: verification-needed-jammy-linux-azure-6.8 ** Tags added: verification-done-jammy-linux-azure-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2076291 Title: kernel panic was caused by a fatal exception due to a null pointer dereference in the iptable_nat module Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Noble: Fix Released Status in linux-azure source package in Oracular: Fix Committed Bug description: [Impact] * Microsoft has requested a patch to address a kernel panic issue similar to the upstream issue here - https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/ [Fix] * Clean cherry-pick upstream commit 5830aa863981: "netfilter: iptables: Fix null-ptr-deref in iptable_nat_table_init()" [Test Plan] * Build and boot tested [Where problems could occur] * Low regression risk, mostly shifting logic * Change to order of register_pernet_subsys() and xt_register_template() could expose some other logic being held together under race condition [Other info] * SF #00391736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2076291/+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
