From: Mark Brown <broonie@kernel.org>
To: Oliver Upton <oupton@kernel.org>, Marc Zyngier <maz@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the kvm-arm-fixes tree
Date: Tue, 7 Jul 2026 13:11:55 +0100 [thread overview]
Message-ID: <akztC7H2IsEKaq4i@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2480 bytes --]
Hi all,
After merging the kvm-arm-fixes tree, today's linux-next build
(arm64 defconfig) started generating warnings:
In file included from /tmp/next/build/include/linux/limits.h:7,
from /tmp/next/build/include/linux/overflow.h:6,
from /tmp/next/build/include/linux/bits.h:32,
from /tmp/next/build/arch/arm64/include/asm/kvm_pgtable.h:10,
from /tmp/next/build/arch/arm64/kvm/hyp/pgtable.c:11:
/tmp/next/build/arch/arm64/kvm/hyp/pgtable.c: In function 'kvm_pgtable_stage2_relax_perms':
/tmp/next/build/include/vdso/limits.h:8:25: warning: overflow in conversion from 'int' to 's8' {aka 'signed char'} changes value from '2147483647' to '-1' [-Woverflow]
8 | #define INT_MAX ((int)(~0U >> 1))
| ^
/tmp/next/build/arch/arm64/include/asm/tlbflush.h:131:33: note: in expansion of macro 'INT_MAX'
131 | #define TLBI_TTL_UNKNOWN INT_MAX
| ^~~~~~~
/tmp/next/build/arch/arm64/kvm/hyp/pgtable.c:1361:20: note: in expansion of macro 'TLBI_TTL_UNKNOWN'
1361 | s8 level = TLBI_TTL_UNKNOWN;
| ^~~~~~~~~~~~~~~~
In file included from /tmp/next/build/include/linux/limits.h:7,
from /tmp/next/build/include/linux/overflow.h:6,
from /tmp/next/build/include/linux/bits.h:32,
from /tmp/next/build/arch/arm64/include/asm/kvm_pgtable.h:10,
from /tmp/next/build/arch/arm64/kvm/hyp/nvhe/../pgtable.c:11:
/tmp/next/build/arch/arm64/kvm/hyp/nvhe/../pgtable.c: In function 'kvm_pgtable_stage2_relax_perms':
/tmp/next/build/include/vdso/limits.h:8:25: warning: overflow in conversion from 'int' to 's8' {aka 'signed char'} changes value from '2147483647' to '-1' [-Woverflow]
8 | #define INT_MAX ((int)(~0U >> 1))
| ^
/tmp/next/build/arch/arm64/include/asm/tlbflush.h:131:33: note: in expansion of macro 'INT_MAX'
131 | #define TLBI_TTL_UNKNOWN INT_MAX
| ^~~~~~~
/tmp/next/build/arch/arm64/kvm/hyp/nvhe/../pgtable.c:1361:20: note: in expansion of macro 'TLBI_TTL_UNKNOWN'
1361 | s8 level = TLBI_TTL_UNKNOWN;
| ^~~~~~~~~~~~~~~~
Caused by commit
100baf0184896 (KVM: arm64: Ensure level is always initialized when relaxing perms)
I imagine this will cause an allyesconfig build failure when I get to
that due to -Werror.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-07 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:11 Mark Brown [this message]
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-07 13:17 ` linux-next: build warnings after merge of the kvm-arm-fixes tree Marc Zyngier
2026-07-07 15:44 ` Oliver Upton
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=akztC7H2IsEKaq4i@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox