From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC pve-kernel 1/2] d/rules: kconfig: disable CONFIG_UBSAN
Date: Mon, 30 May 2022 20:38:46 +0200 [thread overview]
Message-ID: <20220530183848.2816971-2-s.ivanov@proxmox.com> (raw)
In-Reply-To: <20220530183848.2816971-1-s.ivanov@proxmox.com>
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.ivanov@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
next prev parent reply other threads:[~2022-05-30 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 18:38 [pve-devel] [RFC pve-kernel 0/2] disable UBSAN in kernel config Stoiko Ivanov
2022-05-30 18:38 ` Stoiko Ivanov [this message]
2022-05-30 18:38 ` [pve-devel] [RFC pve-kernel 2/2] update ABI file for 5.15.35-2-pve Stoiko Ivanov
2022-05-31 5:39 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220530183848.2816971-2-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox