From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Sean Christopherson <seanjc@google.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: Hang when booting guest kernels compiled with clang after SRSO mitigations
Date: Sat, 12 Aug 2023 07:31:30 -0700 [thread overview]
Message-ID: <20230812143130.GA3494185@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230812134642.GGZNeNQpebzu3H3NDh@fat_crate.local>
On Sat, Aug 12, 2023 at 03:46:42PM +0200, Borislav Petkov wrote:
> Btw, this:
>
> https://github.com/ClangBuiltLinux/linux/commit/150c42407f87463c27a2459e06845965291d9973
>
> Is this fixing a current issue and so it needs to go to Linus now?
>
> If so, I'll expedite it too.
Yes, that fixes an error at link time when building with LTO:
https://github.com/ClangBuiltLinux/linux/issues/1909
That is commit 973ab2d61f33 ("x86/retpoline,kprobes: Fix position of
thunk sections with CONFIG_LTO_CLANG") in x86/core, with the conflicts
against SRSO resolved and the fix that Andrew Cooper pointed out
squashed in, in case my comment in the commit message was not clear
enough :)
https://lore.kernel.org/lkml/20230803230323.1478869-1-andrew.cooper3@citrix.com/
With that change and the other ld.lld change you already picked up in
x86/bugs, our builds should go back to green, then we can decide what to
do about that runtime warning based on Peter's series and Nick's ability
to get back up and running (I have his patch applied locally somewhere
so I don't mind collecting tags and sending it next week).
Thanks again for helping us with this, I know it has been chaotic.
Cheers,
Nathan
prev parent reply other threads:[~2023-08-12 14:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:33 Hang when booting guest kernels compiled with clang after SRSO mitigations Nathan Chancellor
2023-08-10 8:10 ` Borislav Petkov
2023-08-10 9:08 ` Borislav Petkov
2023-08-10 9:15 ` Borislav Petkov
2023-08-10 10:16 ` Nathan Chancellor
2023-08-10 12:51 ` Borislav Petkov
2023-08-10 13:27 ` Nathan Chancellor
2023-08-10 13:32 ` Borislav Petkov
2023-08-10 13:40 ` Nathan Chancellor
2023-08-10 14:43 ` Borislav Petkov
2023-08-10 15:07 ` Nathan Chancellor
2023-08-10 15:14 ` Borislav Petkov
2023-08-10 15:48 ` Nathan Chancellor
2023-08-10 16:14 ` Nathan Chancellor
2023-08-11 10:14 ` Borislav Petkov
2023-08-11 14:09 ` Nathan Chancellor
2023-08-11 16:03 ` Sean Christopherson
2023-08-11 16:12 ` Borislav Petkov
2023-08-12 0:42 ` Nick Desaulniers
2023-08-12 13:46 ` Borislav Petkov
2023-08-12 14:31 ` Nathan Chancellor [this message]
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=20230812143130.GA3494185@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
--cc=seanjc@google.com \
--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