All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Grygorii Strashko <grygorii_strashko@epam.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: X86: build failure
Date: Tue, 16 Dec 2025 23:54:00 +0000	[thread overview]
Message-ID: <63b6f29f-29ca-458e-8d6f-3408e84173e9@citrix.com> (raw)
In-Reply-To: <8ee2e801-9a3a-414d-9df9-113f419e02e9@epam.com>

On 16/12/2025 11:35 pm, Grygorii Strashko wrote:
> Hi All,
>
> I experience build failure with following Kconfig combination:
>  CONFIG_DEBUG=n and CONFIG_XEN_IBT=n
>
> with gcc:
>  gcc --version
>  gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0
>  Copyright (C) 2021 Free Software Foundation, Inc.
>  This is free software; see the source for copying conditions.  There
> is NO
>  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
>
> Is this known issue?
>
> ====== log ===============
>   CC      arch/x86/x86_emulate.o
> In file included from arch/x86/x86_emulate.c:27:
> arch/x86/x86_emulate/x86_emulate.c: In function ‘x86_emulate’:
> arch/x86/x86_emulate/x86_emulate.c:70:36: error: writing 1 byte into a
> region of size 0 [-Werror=stringop-overflow=]
>    70 |     gcc11_wrap(ptr)[0 - PFX_BYTES] = ext < ext_8f08 ? 0xc4 :
> 0x8f; \
> arch/x86/x86_emulate/x86_emulate.c:78:9: note: in expansion of macro
> ‘copy_VEX’
>    78 |         copy_VEX(ptr, vex); \
>       |         ^~~~~~~~
> arch/x86/x86_emulate/x86_emulate.c:8140:13: note: in expansion of
> macro ‘copy_REX_VEX’
>  8140 |             copy_REX_VEX(opc, rex_prefix, vex);
>       |             ^~~~~~~~~~~~
> In file included from arch/x86/x86_emulate/x86_emulate.c:11,
>                  from arch/x86/x86_emulate.c:27:
> arch/x86/x86_emulate/private.h:691:17: note: at offset [0, 4095] into
> destination object of size [0, 9223372036854775807] allocated by
> ‘map_domain_page’
>   691 |     (stb).ptr = map_domain_page(_mfn(this_cpu(stubs.mfn))) + \
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/x86/x86_emulate/x86_emulate.c:60:21: note: in expansion of macro
> ‘get_stub’
>    60 |     uint8_t *buf_ = get_stub(stub); \
>       |                     ^~~~~~~~
> arch/x86/x86_emulate/x86_emulate.c:3354:15: note: in expansion of
> macro ‘init_prefixes’
>  3354 |         opc = init_prefixes(stub);
>       |               ^~~~~~~~~~~~~
> arch/x86/x86_emulate/private.h:691:17: note: at offset [1, 4096] into
> destination object of size [0, 9223372036854775807] allocated by
> ‘map_domain_page’
>   691 |     (stb).ptr = map_domain_page(_mfn(this_cpu(stubs.mfn))) + \
>       |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/x86/x86_emulate/x86_emulate.c:94:21: note: in expansion of macro
> ‘get_stub’
>    94 |     uint8_t *buf_ = get_stub(stub); \
>       |                     ^~~~~~~~
> arch/x86/x86_emulate/x86_emulate.c:3402:15: note: in expansion of
> macro ‘init_evex’
>  3402 |         opc = init_evex(stub);
> [...]
>

Hmm - that looks like more of the GCC 11 bounds bugs, but that's what
the gcc11_wrap() visible at the top is supposed to be fixing.

Neither of those CONFIG options ought to be relevant.

Which Ubuntu is this?  Is it something local, or from one of our CI
containers?  Is this on staging, or local?

~Andrew


  reply	other threads:[~2025-12-16 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 23:35 X86: build failure Grygorii Strashko
2025-12-16 23:54 ` Andrew Cooper [this message]
2025-12-17  0:12   ` Grygorii Strashko
2025-12-17  7:13     ` Nicola Vetrini
2025-12-17  7:14       ` Nicola Vetrini
2025-12-17  7:47   ` Jan Beulich

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=63b6f29f-29ca-458e-8d6f-3408e84173e9@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=grygorii_strashko@epam.com \
    --cc=xen-devel@lists.xenproject.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.