[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023051711-thespian-sponsor-8878@gregkh>
Date: Wed, 17 May 2023 10:51:03 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@...il.com>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com, srw@...dewatkins.net,
rwarsow@....de
Subject: Re: [PATCH 5.10 000/381] 5.10.180-rc1 review
On Tue, May 16, 2023 at 10:14:36AM +0100, Sudip Mukherjee (Codethink) wrote:
> Hi Greg,
>
> On Mon, May 15, 2023 at 06:24:11PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.180 release.
> > There are 381 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
>
> Build test (gcc version 11.3.1 20230511):
> mips: 63 configs -> no failure
> arm: 104 configs -> no failure
> arm64: 3 configs -> 1 failure
> x86_64: 4 configs -> no failure
> alpha allmodconfig -> no failure
> powerpc allmodconfig -> no failure
> riscv allmodconfig -> no failure
> s390 allmodconfig -> no failure
> xtensa allmodconfig -> no failure
>
> arm64 allmodconfig build fails with the error:
>
> /gcc/bin/aarch64-linux-ld: arch/arm64/kvm/hyp/nvhe/kvm_nvhe.o: in function `__kvm_nvhe___kvm_tlb_flush_vmid_ipa':
> (.hyp.text+0x1a4c): undefined reference to `__kvm_nvhe_memset'
> /gcc/bin/aarch64-linux-ld: arch/arm64/kvm/hyp/nvhe/kvm_nvhe.o: in function `__kvm_nvhe___kvm_tlb_flush_vmid':
> (.hyp.text+0x1b20): undefined reference to `__kvm_nvhe_memset'
> /gcc/bin/aarch64-linux-ld: arch/arm64/kvm/hyp/nvhe/kvm_nvhe.o: in function `__kvm_nvhe___kvm_flush_cpu_context':
> (.hyp.text+0x1b80): undefined reference to `__kvm_nvhe_memset'
That's odd, I don't see that symbol anywhere in the tree at all.
And the only arm-related kvm changes don't have those symbols either
(the other kvm changes are x86-only)
Also, no one else has seen this issue. Can you bisect?
thanks,
greg k-h
Powered by blists - more mailing lists