From: Nathan Chancellor <nathan@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] x86/sev: Disable UBSAN on SEV code that may execute very early
Date: Wed, 1 Jan 2025 15:30:08 -0700 [thread overview]
Message-ID: <20250101223008.GA2803252@ax162> (raw)
In-Reply-To: <20250101115119.114584-2-ardb@kernel.org>
On Wed, Jan 01, 2025 at 12:51:20PM +0100, Ard Biesheuvel wrote:
> Clang 14 and older may emit UBSAN instrumentation into code that is
> inlined into functions marked with __no_sanitize_undefined. This may
> result in faults when the code is executed very early, which may be the
> case for functions annotated as __head. Now that this requirement is
> strictly enforced, the build will fail in this case with the following
> message
>
> Absolute reference to symbol '.data' not permitted in .head.text
>
> Work around this by disabling UBSAN instrumentation on all SEV core
> code.
>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Seems reasonable to me.
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> arch/x86/coco/sev/Makefile | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/coco/sev/Makefile b/arch/x86/coco/sev/Makefile
> index 4e375e7305ac..08de37559307 100644
> --- a/arch/x86/coco/sev/Makefile
> +++ b/arch/x86/coco/sev/Makefile
> @@ -13,3 +13,6 @@ KCOV_INSTRUMENT_core.o := n
> # With some compiler versions the generated code results in boot hangs, caused
> # by several compilation units. To be safe, disable all instrumentation.
> KCSAN_SANITIZE := n
> +
> +# Clang 14 and older may fail to respect __no_sanitize_undefined when inlining
> +UBSAN_SANITIZE := n
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-01-01 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 11:51 [PATCH] x86/sev: Disable UBSAN on SEV code that may execute very early Ard Biesheuvel
2025-01-01 22:30 ` Nathan Chancellor [this message]
2025-01-02 12:01 ` [tip: x86/boot] " tip-bot2 for Ard Biesheuvel
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=20250101223008.GA2803252@ax162 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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