From: no-reply@sashiko.virtuozzo.com
To: devel@openvz.org, Konstantin Khorenko <khorenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH hci-8.1 v2] configs: build with WERROR and KVM_WERROR, as RHEL does
Date: Tue, 27 Oct 2026 15:11:55 +0000 [thread overview]
Message-ID: <010701a17deb0247-72a58f6c-80f7-42b5-bd71-056e1997c97a-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261027-b4-prep-khorenko-vstor-151903-werror-v2-1-b77e17cc3b3d@virtuozzo.com>
> 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>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261027-b4-prep-khorenko-vstor-151903-werror-v2-1-b77e17cc3b3d@virtuozzo.com?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-27 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:08 Konstantin Khorenko
2026-10-27 15:11 ` no-reply [this message]
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=010701a17deb0247-72a58f6c-80f7-42b5-bd71-056e1997c97a-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.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