From: Oliver Upton <oliver.upton@linux.dev>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org
Subject: Re: v6.6.33-rc1 build failure
Date: Tue, 4 Jun 2024 11:41:29 -0700 [thread overview]
Message-ID: <Zl9f2XgKaFgS-G3i@linux.dev> (raw)
In-Reply-To: <b4cc4d63-3c68-46ba-8803-d072aad11793@sirena.org.uk>
Hey,
Thanks for flagging this broonie.
On Tue, Jun 04, 2024 at 02:35:20PM +0100, Mark Brown wrote:
> I'm not seeing a test mail for v6.6.33-rc1 but it's in the stable-rc git
> and I'm seeing build failures in the KVM selftests for arm64 with it:
>
> /usr/bin/ld: /build/stage/build-work/kselftest/kvm/aarch64/vgic_init.o: in funct
> ion `test_v2_uaccess_cpuif_no_vcpus':
> /build/stage/linux/tools/testing/selftests/kvm/aarch64/vgic_init.c:388:(.text+0x
> 1234): undefined reference to `FIELD_PREP'
> /usr/bin/ld: /build/stage/linux/tools/testing/selftests/kvm/aarch64/vgic_init.c:
> 388:(.text+0x1244): undefined reference to `FIELD_PREP'
> /usr/bin/ld: /build/stage/linux/tools/testing/selftests/kvm/aarch64/vgic_init.c:
> 393:(.text+0x12a4): undefined reference to `FIELD_PREP'
> /usr/bin/ld: /build/stage/linux/tools/testing/selftests/kvm/aarch64/vgic_init.c:
> 393:(.text+0x12b4): undefined reference to `FIELD_PREP'
> /usr/bin/ld: /build/stage/linux/tools/testing/selftests/kvm/aarch64/vgic_init.c:
> 398:(.text+0x1308): undefined reference to `FIELD_PREP'
>
> due to 12237178b318fb3 ("KVM: selftests: Add test for uaccesses to
> non-existent vgic-v2 CPUIF") which was backported from
> 160933e330f4c5a13931d725a4d952a4b9aefa71.
Yeah, so this is likely because commit 0359c946b131 ("tools headers arm64:
Update sysreg.h with kernel sources") upstream got this test to indirectly
include bitfield.h. We should *not* backport the patch that fixes it,
though.
Let's either squash in the following, or just drop the offending patch
altogether.
--
Thanks,
Oliver
From 5a957ab6d80f4fcb4b1f2bcbd5b999fde003bffd Mon Sep 17 00:00:00 2001
From: Oliver Upton <oliver.upton@linux.dev>
Date: Tue, 4 Jun 2024 18:36:29 +0000
Subject: [PATCH] fixup! KVM: selftests: Add test for uaccesses to non-existent
vgic-v2 CPUIF
commit 0359c946b131 ("tools headers arm64: Update sysreg.h with kernel
sources") upstream indirectly included bitfield.h, which is a dependency
of this patch. Work around the situation locally by directly including
bitfield.h in the test.
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
---
tools/testing/selftests/kvm/aarch64/vgic_init.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/kvm/aarch64/vgic_init.c b/tools/testing/selftests/kvm/aarch64/vgic_init.c
index ca917c71ff60..4ac4d3ea976e 100644
--- a/tools/testing/selftests/kvm/aarch64/vgic_init.c
+++ b/tools/testing/selftests/kvm/aarch64/vgic_init.c
@@ -6,6 +6,7 @@
*/
#define _GNU_SOURCE
#include <linux/kernel.h>
+#include <linux/bitfield.h>
#include <sys/syscall.h>
#include <asm/kvm.h>
#include <asm/kvm_para.h>
--
2.45.1.467.gbab1589fc0-goog
next prev parent reply other threads:[~2024-06-04 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 13:35 v6.6.33-rc1 build failure Mark Brown
2024-06-04 18:41 ` Oliver Upton [this message]
2024-06-06 13:02 ` Greg Kroah-Hartman
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=Zl9f2XgKaFgS-G3i@linux.dev \
--to=oliver.upton@linux.dev \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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 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.