From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: [Devel] [PATCH hci-8.1 v2] configs: build with WERROR and KVM_WERROR, as RHEL does
Date: Tue, 27 Oct 2026 16:08:15 +0100 [thread overview]
Message-ID: <20261027-b4-prep-khorenko-vstor-151903-werror-v2-1-b77e17cc3b3d@virtuozzo.com> (raw)
RHEL generates its configs in "make dist-srpm": the redhat/Makefile
dist-* targets export ENABLE_WERROR=1, and build_configs.sh then turns
CONFIG_WERROR, CONFIG_KVM_WERROR and CONFIG_OBJTOOL_WERROR on in every
config.
We call build_configs.sh directly, without ENABLE_WERROR, so the vz
kernel builds without -Werror and a new warning goes unnoticed.
We already have CONFIG_OBJTOOL_WERROR=y due to work on KLP, so set
CONFIG_WERROR and CONFIG_KVM_WERROR in custom-overrides/generic as well.
Like ENABLE_WERROR, they reach every flavor, the debug one included.
The um variant, the User Mode Linux KUnit kernel, does not build with
-Werror yet, so custom-overrides/generic/um/CONFIG_WERROR keeps it off
there.
https://virtuozzo.atlassian.net/browse/VSTOR-151903
Feature: internal
Signed-off-by: Konstantin Khorenko <khorenko@virtuozzo.com>
---
Assisted-by: LLM
---
Changes in v2:
- Name the um layer file that keeps WERROR off, not the generated
kernel-um-rhel.config, which the kernel tree does not carry.
- Say the overrides reach every flavor, as ENABLE_WERROR does.
- Fix the target name: dist-srpm.
- Link to v1: http://lore.virtuozzo.com/20261027-b4-prep-khorenko-vstor-151903-werror-v1-1-00b3a34049dd@virtuozzo.com
---
redhat/configs/custom-overrides/generic/CONFIG_KVM_WERROR | 1 +
redhat/configs/custom-overrides/generic/CONFIG_WERROR | 1 +
2 files changed, 2 insertions(+)
diff --git a/redhat/configs/custom-overrides/generic/CONFIG_KVM_WERROR b/redhat/configs/custom-overrides/generic/CONFIG_KVM_WERROR
new file mode 100644
index 0000000000000..af20cbee74354
--- /dev/null
+++ b/redhat/configs/custom-overrides/generic/CONFIG_KVM_WERROR
@@ -0,0 +1 @@
+CONFIG_KVM_WERROR=y
diff --git a/redhat/configs/custom-overrides/generic/CONFIG_WERROR b/redhat/configs/custom-overrides/generic/CONFIG_WERROR
new file mode 100644
index 0000000000000..f54ff6cdaab85
--- /dev/null
+++ b/redhat/configs/custom-overrides/generic/CONFIG_WERROR
@@ -0,0 +1 @@
+CONFIG_WERROR=y
---
base-commit: 39277db2080bec85a02c245ac0d7d185b37cdfdd
change-id: 20261027-b4-prep-khorenko-vstor-151903-werror-33b973335ad5
Best regards,
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-10-27 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:08 Konstantin Khorenko [this message]
2026-10-27 15:11 ` no-reply
2026-10-27 15:42 ` Konstantin Khorenko
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=20261027-b4-prep-khorenko-vstor-151903-werror-v2-1-b77e17cc3b3d@virtuozzo.com \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.