While UBSAN helps in improving the kernel codebase, and with the current config (CONFIG_UBSAN_TRAP is disabled), UBSAN should only print warnings and not panic, it still can look scary to users, who are upgrading from the previous kernel series (5.13/ubuntu-impish had UBSAN disabled, it got reenabled with 5.15.0-14.14/ ddcf9715e1d13cea21ac90014f848e0c4c0ad23c last December)
based on reports about UBSAN warnings in our community-forum: https://forum.proxmox.com/threads/.110097/ https://forum.proxmox.com/threads/.109368/ Signed-off-by: Stoiko Ivanov <s.iva...@proxmox.com> --- debian/rules | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 1ec1147..d6e4fe9 100755 --- a/debian/rules +++ b/debian/rules @@ -83,7 +83,8 @@ PVE_CONFIG_OPTS= \ -d CONFIG_SECURITY_LOCKDOWN_LSM \ -d CONFIG_SECURITY_LOCKDOWN_LSM_EARLY \ --set-str CONFIG_LSM yama,integrity,apparmor \ --e CONFIG_PAGE_TABLE_ISOLATION +-e CONFIG_PAGE_TABLE_ISOLATION \ +-d CONFIG_UBSAN debian/control: $(wildcard debian/*.in) sed -e 's/@@KVNAME@@/${KVNAME}/g' < debian/pve-kernel.prerm.in > debian/${PVE_KERNEL_PKG}.prerm -- 2.30.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
