[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Changed in: linux-azure (Ubuntu Noble) Status: In Progress => 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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
https://lists.ubuntu.com/archives/kernel-team/2024-February/148724.html -- 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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP 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 Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug is awaiting verification that the linux-azure/5.15.0-1058.66 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-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP 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 Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP 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 Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 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-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP 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 Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-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/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP 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 Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug was fixed in the package linux-azure - 6.8.0-1001.1 --- linux-azure (6.8.0-1001.1) noble; urgency=medium * noble/linux-azure: 6.8.0-1001.1 -proposed tracker (LP: #2052777) * Packaging resync (LP: #1786013) - debian.azure/dkms-versions -- update from kernel-versions (main/d2024.02.07) * Azure: cifs modules missing from the linux-modules package (LP: #2052980) - [Config] Move cifs.ko to linux-modules package * Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723) - [Config] CONFIG_TEST_LOCKUP=m * Miscellaneous Ubuntu changes - [Packaging] azure: update Rust toolchain - [Packaging] azure: move to kernel v6.8 - [Config] azure: update annotations after moving to v6.8 [ Ubuntu: 6.8.0-9.9 ] * noble/linux: 6.8.0-9.9 -proposed tracker (LP: #2052945) * Miscellaneous upstream changes - Revert "UBUNTU: [Packaging] temporarily disable Rust dependencies on riscv64" [ Ubuntu: 6.8.0-8.8 ] * noble/linux: 6.8.0-8.8 -proposed tracker (LP: #2052918) * Miscellaneous Ubuntu changes - [Packaging] riscv64: enable linux-libc-dev build - v6.8-rc4 rebase * Rebase on v6.8-rc4 [ 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: apparmo
[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug was fixed in the package linux-azure - 5.15.0-1058.66 --- linux-azure (5.15.0-1058.66) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1058.66 -proposed tracker (LP: #2052049) * Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723) - [Config] CONFIG_TEST_LOCKUP=m [ Ubuntu: 5.15.0-100.110 ] * jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616) * i915 regression introduced with 5.5 kernel (LP: #2044131) - drm/i915: Skip some timing checks on BXT/GLK DSI transcoders * Audio balancing setting doesn't work with the cirrus codec (LP: #2051050) - ALSA: hda/cs8409: Suppress vmaster control for Dolphin models * partproke is broken on empty loopback device (LP: #2049689) - block: Move checking GENHD_FL_NO_PART to bdev_add_partition() * CVE-2023-0340 - vhost: use kzalloc() instead of kmalloc() followed by memset() * CVE-2023-51780 - atm: Fix Use-After-Free in do_vcc_ioctl * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * CVE-2024-0646 - net: tls, update curr on splice as well * CVE-2024-0565 - smb: client: fix OOB in receive_encrypted_standard() * CVE-2023-51781 - appletalk: Fix Use-After-Free in atalk_ioctl * Jammy update: v5.15.143 upstream stable release (LP: #2050858) - vdpa/mlx5: preserve CVQ vringh index - hrtimers: Push pending hrtimers away from outgoing CPU earlier - i2c: designware: Fix corrupted memory seen in the ISR - netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test - tg3: Move the [rt]x_dropped counters to tg3_napi - tg3: Increment tx_dropped in tg3_tso_bug() - kconfig: fix memory leak from range properties - drm/amdgpu: correct chunk_ptr to a pointer to chunk. - platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum - platform/x86: asus-wmi: Add support for ROG X13 tablet mode - platform/x86: asus-wmi: Simplify tablet-mode-switch probing - platform/x86: asus-wmi: Simplify tablet-mode-switch handling - platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi code - of: dynamic: Fix of_reconfig_get_state_change() return value documentation - platform/x86: wmi: Allow duplicate GUIDs for drivers that use struct wmi_driver - platform/x86: wmi: Skip blocks with zero instances - ipv6: fix potential NULL deref in fib6_add() - octeontx2-pf: Add missing mutex lock in otx2_get_pauseparam - octeontx2-af: Check return value of nix_get_nixlf before using nixlf - hv_netvsc: rndis_filter needs to select NLS - r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE - r8152: Add RTL8152_INACCESSIBLE checks to more loops - r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash() - r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1() - r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en() - mlxbf-bootctl: correctly identify secure boot with development keys - platform/mellanox: Add null pointer checks for devm_kasprintf() - platform/mellanox: Check devm_hwmon_device_register_with_groups() return value - arcnet: restoring support for multiple Sohard Arcnet cards - net: stmmac: fix FPE events losing - octeontx2-af: fix a use-after-free in rvu_npa_register_reporters - i40e: Fix unexpected MFS warning message - net: bnxt: fix a potential use-after-free in bnxt_init_tc - ionic: fix snprintf format length warning - ionic: Fix dim work handling in split interrupt mode - ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() - net: hns: fix fake link up on xge port - octeontx2-af: Update Tx link register range - netfilter: nf_tables: validate family when identifying table via handle - netfilter: xt_owner: Fix for unsafe access of sk->sk_socket - tcp: do not accept ACK of bytes we never sent - bpf: sockmap, updating the sg structure should also update curr - psample: Require 'CAP_NET_ADMIN' when joining "packets" group - net: add missing kdoc for struct genl_multicast_group::flags - drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group - tee: optee: Fix supplicant based device enumeration - RDMA/hns: Fix unnecessary err return when using invalid congest control algorithm - RDMA/irdma: Do not modify to SQD on error - RDMA/irdma: Add wait for suspend on SQD - arm64: dts: rockchip: Expand reg size of vdec node for RK3399 - RDMA/rtrs-srv: Do not unconditionally enable irq - RDMA/rtrs-clt: Start hb after path_up - RDMA/rtrs-srv: Check return values while processing info request - RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true - RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight - RDMA/rtrs-clt: Fix the max_send_wr setting - RDMA/rtrs-clt: Remove the warnings for req in_use check - RDMA/bnxt_re: Correct module description string - hwmon: (acpi_powe
