From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: 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: Thu, 10 Aug 2023 06:40:56 -0700 [thread overview]
Message-ID: <20230810134056.GA130730@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230810133216.GKZNTm4KpohRR4gVsT@fat_crate.local>
On Thu, Aug 10, 2023 at 03:32:16PM +0200, Borislav Petkov wrote:
> On Thu, Aug 10, 2023 at 06:27:06AM -0700, Nathan Chancellor wrote:
> > But my host kernel was compiled using GCC 13.2.0 from kernel.org for the
> > sake of testing to see if the compiler used to build the host kernel had
> > an impact on the problem and it did not.
>
> Ok, now I'm confused.
Heh, so was I at first when I was doing my regular build and boot tests
of -next :P
> Lemme see if I understand it correctly:
>
> host kernel:
> - SRSO enabled
> - built with gcc
>
> guest kernel:
> - built with clang
> - SRSO not necessary
>
> Is that the scenario?
Yes, that should be correct.
Host kernel string:
6.5.0-rc5-00039-g138bcddb86d8 (nathan@dev-arch.thelio-3990X) (x86_64-linux-gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.41) #1 SMP PREEMPT_DYNAMIC Wed Aug 9 17:34:43 MST 2023
Guest kernel string:
6.5.0-rc5 (nathan@dev-arch.thelio-3990X) (ClangBuiltLinux clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6), GNU ld (GNU Binutils) 2.41.50.20230809) #1 SMP PREEMPT_DYNAMIC Wed Aug 9 16:54:33 MST 2023
> Anything else?
Shouldn't be. As I noted in the original email, it seems something
specific to the safe-ret mitigation as I don't see the problem with
ibpb, that would be a good canary for making sure that you see the same
behavior.
Cheers,
Nathan
next prev parent reply other threads:[~2023-08-10 13:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 1:33 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 [this message]
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
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=20230810134056.GA130730@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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
all inboxes | Powered by JetHome®