From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 01E7B73DE1 for ; Mon, 30 May 2022 20:39:03 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 00270CCB for ; Mon, 30 May 2022 20:39:03 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 68757CBD for ; Mon, 30 May 2022 20:39:01 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 3F81A43964 for ; Mon, 30 May 2022 20:39:01 +0200 (CEST) From: Stoiko Ivanov To: pve-devel@lists.proxmox.com Date: Mon, 30 May 2022 20:38:46 +0200 Message-Id: <20220530183848.2816971-2-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220530183848.2816971-1-s.ivanov@proxmox.com> References: <20220530183848.2816971-1-s.ivanov@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.195 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [RFC pve-kernel 1/2] d/rules: kconfig: disable CONFIG_UBSAN X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2022 18:39:03 -0000 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 --- 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