[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512
This bug was fixed in the package linux-oracle - 6.8.0-1001.1 --- linux-oracle (6.8.0-1001.1) noble; urgency=medium * noble/linux-oracle: 6.8.0-1001.1 -proposed tracker (LP: #2052776) * Packaging resync (LP: #1786013) - debian.oracle/dkms-versions -- update from kernel-versions (main/d2024.02.07) * [arm64] Increase max CPU count to 512 (LP: #2046184) - [Config]: oracle: Increase max CPU count to 512 * Miscellaneous Ubuntu changes - [Config] updateconfigs following 6.8.0-7.7 rebase [ Ubuntu: 6.8.0-7.7 ] * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691) * update apparmor and LSM stacking patch set (LP: #2028253) - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate ima_filter_rule from security_audit_rule - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure management of the sock security - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data structure. - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions with stacked LSMs - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in security_audit_rule_match - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx hook - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob in audit_context - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in security_ipc_getsecid - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM data - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in security_current_getsecid - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in security_inode_getsecid - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in audit_names - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new security_cred_getlsmblob LSM hook - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data from secid to lsmblob - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for audit data - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM context releaser - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in security_secid_to_secctx - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in security_lsmblob_to_secctx - SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in security_inode_getsecctx - SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in security_dentry_init_security - SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM: security_lsmblob_to_secctx module selection - SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp structure - SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple records in an audit_buffer - SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for multiple task security contexts - SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject lsm values for netlabel - SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for multiple object contexts - SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused lsmcontext_init() - SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in security_getprocattr - SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check on release - SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark usage - SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM handles the context string - SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the exclusive flag - SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob size tracking - SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts blobs instead of module specific data - SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure management of the key security blob - SAUCE: apparmor4.0.0 [37/87]: LSM stacking v39: LSM: Infrastructure management of the mnt_opts security blob - SAUCE: apparmor4.0.0 [38/87]: LSM stacking v39: LSM: Correct handling of ENOSYS in inode_setxattr - SAUCE: apparmor4.0.0 [39/87]: LSM stacking v39: LSM: Remove lsmblob scaffolding - SAUCE: apparmor4.0.0 [40/87]: LSM stacking v39: LSM: Allow reservation of netlabel - SAUCE: apparmor4.0.0 [41/87]: LSM stacking v39: LSM: restrict security_cred_getsecid() to a single LSM - SAUCE: apparmor4.0.0 [42/87]: LSM stacking v39: Smack: Remove LSM_FLAG_EXCLUSIVE - SAUCE:
[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512
** Tags removed: verification-needed-jammy-linux-oracle verification-needed-mantic-linux-oracle ** Tags added: verification-done-jammy-linux-oracle 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/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 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 2046184] Re: [arm64] Increase max CPU count to 512
This bug is awaiting verification that the linux-oracle/5.15.0-1051.57 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-done- jammy-linux-oracle'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oracle' to 'verification-failed-jammy- linux-oracle'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oracle-v2 verification-needed-jammy-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/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: 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 2046184] Re: [arm64] Increase max CPU count to 512
This bug was fixed in the package linux-oracle - 6.5.0-1014.14 --- linux-oracle (6.5.0-1014.14) mantic; urgency=medium * mantic/linux-oracle: 6.5.0-1014.14 -proposed tracker (LP: #2048542) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts * [arm64] Increase max CPU count to 512 (LP: #2046184) - [Config]: oracle: Increase max CPU count to 512 [ Ubuntu: 6.5.0-15.15 ] * mantic/linux: 6.5.0-15.15 -proposed tracker (LP: #2048549) * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6606 - smb: client: fix OOB in smbCalcSize() * CVE-2023-6817 - netfilter: nft_set_pipapo: skip inactive elements during set walk * CVE-2023-6932 - ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet * CVE-2023-6931 - perf: Fix perf_event_validate_size() - perf: Fix perf_event_validate_size() lockdep splat -- John Cabaj Thu, 11 Jan 2024 13:15:55 -0600 ** Changed in: linux-oracle (Ubuntu Mantic) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6606 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6817 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6931 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6932 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-0193 -- 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: 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 2046184] Re: [arm64] Increase max CPU count to 512
This bug is awaiting verification that the linux-oracle/6.5.0-1014.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-oracle' to 'verification-done- mantic-linux-oracle'. If the problem still exists, change the tag 'verification-needed-mantic-linux-oracle' to 'verification-failed- mantic-linux-oracle'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-oracle-v2 verification-needed-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/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 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Jammy) Importance: Undecided => Medium -- 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 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 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Mantic) Importance: Undecided => Medium -- 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: In Progress 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
