From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "François Valenduc" <francoisvalenduc@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.1.64
Date: Tue, 28 Nov 2023 19:30:34 +0000 [thread overview]
Message-ID: <2023112854-filth-diaper-1a20@gregkh> (raw)
In-Reply-To: <7f07bb2d-bb00-4774-8cc0-d66b7210380c@gmail.com>
On Tue, Nov 28, 2023 at 08:22:22PM +0100, François Valenduc wrote:
> Build fails on my baremetal server on scaleway:
>
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:215:20: note: previous definition of
> ‘evmptr_is_valid’ with type ‘bool(u64)’ {aka ‘_Bool(long long unsigned
> int)’}
> 215 | static inline bool evmptr_is_valid(u64 evmptr)
> | ^~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:55:
> arch/x86/kvm/vmx/hyperv.h:184:6: error: redeclaration of ‘enum
> nested_evmptrld_status’
> 184 | enum nested_evmptrld_status {
> | ^~~~~~~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:220:6: note: originally defined here
> 220 | enum nested_evmptrld_status {
> | ^~~~~~~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:55:
> arch/x86/kvm/vmx/hyperv.h:185:9: error: redeclaration of enumerator
> ‘EVMPTRLD_DISABLED’
> 185 | EVMPTRLD_DISABLED,
> | ^~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:221:9: note: previous definition of
> ‘EVMPTRLD_DISABLED’ with type ‘enum nested_evmptrld_status’
> 221 | EVMPTRLD_DISABLED,
> | ^~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:55:
> arch/x86/kvm/vmx/hyperv.h:186:9: error: redeclaration of enumerator
> ‘EVMPTRLD_SUCCEEDED’
> 186 | EVMPTRLD_SUCCEEDED,
> | ^~~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:222:9: note: previous definition of
> ‘EVMPTRLD_SUCCEEDED’ with type ‘enum nested_evmptrld_status’
> 222 | EVMPTRLD_SUCCEEDED,
> | ^~~~~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:55:
> arch/x86/kvm/vmx/hyperv.h:187:9: error: redeclaration of enumerator
> ‘EVMPTRLD_VMFAIL’
> 187 | EVMPTRLD_VMFAIL,
> | ^~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:223:9: note: previous definition of
> ‘EVMPTRLD_VMFAIL’ with type ‘enum nested_evmptrld_status’
> 223 | EVMPTRLD_VMFAIL,
> | ^~~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:55:
> arch/x86/kvm/vmx/hyperv.h:188:9: error: redeclaration of enumerator
> ‘EVMPTRLD_ERROR’
> 188 | EVMPTRLD_ERROR,
> | ^~~~~~~~~~~~~~
> In file included from arch/x86/kvm/vmx/vmx.c:54:
> arch/x86/kvm/vmx/evmcs.h:224:9: note: previous definition of
> ‘EVMPTRLD_ERROR’ with type ‘enum nested_evmptrld_status’
> 224 | EVMPTRLD_ERROR,
> | ^~~~~~~~~~~~~~
> make[3]: *** [scripts/Makefile.build:250: arch/x86/kvm/vmx/vmx.o] Error 1
> make[2]: *** [scripts/Makefile.build:500: arch/x86/kvm] Error 2
> make[1]: *** [scripts/Makefile.build:500: arch/x86] Error 2
>
> The configuration file is attached. Kernel 6.1.62 compiled fine.
> Does somebody have an idea about this ?
That's odd, any chance you can run 'git bisect' to track down the
offending commit?
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-28 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 18:25 Linux 6.1.64 Greg Kroah-Hartman
2023-11-28 18:25 ` Greg Kroah-Hartman
2023-11-28 19:22 ` François Valenduc
2023-11-28 19:22 ` François Valenduc
2023-11-28 19:30 ` Greg Kroah-Hartman [this message]
2023-11-28 19:35 ` Greg Kroah-Hartman
2023-11-28 19:37 ` François Valenduc
2023-11-28 21:11 ` François Valenduc
2023-11-28 21:18 ` 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=2023112854-filth-diaper-1a20@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=francoisvalenduc@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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