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 09:14:14 -0700 [thread overview]
Message-ID: <20230810161414.GA4000@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230810154831.GA38495@dev-arch.thelio-3990X>
On Thu, Aug 10, 2023 at 08:48:31AM -0700, Nathan Chancellor wrote:
> On Thu, Aug 10, 2023 at 05:14:10PM +0200, Borislav Petkov wrote:
> > Also, can you bisect rc5..master to see which exact patch is causing
> > this?
>
> Sure thing. I at least isolated it to the SRSO merge, so I will just
> bisect that to see the exact commit that causes this.
Heh, figured this would be the case:
# bad: [138bcddb86d8a4f842e4ed6f0585abc9b1a764ff] Merge tag 'x86_bugs_srso' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
# good: [14f9643dc90adea074a0ffb7a17d337eafc6a5cc] Merge tag 'wq-for-6.5-rc5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
git bisect start '138bcddb86d8a4f842e4ed6f0585abc9b1a764ff' '14f9643dc90adea074a0ffb7a17d337eafc6a5cc'
# bad: [233d6f68b98d480a7c42ebe78c38f79d44741ca9] x86/srso: Add IBPB
git bisect bad 233d6f68b98d480a7c42ebe78c38f79d44741ca9
# bad: [fb3bd914b3ec28f5fb697ac55c4846ac2d542855] x86/srso: Add a Speculative RAS Overflow mitigation
git bisect bad fb3bd914b3ec28f5fb697ac55c4846ac2d542855
# good: [0e52740ffd10c6c316837c6c128f460f1aaba1ea] x86/bugs: Increase the x86 bugs vector size to two u32s
git bisect good 0e52740ffd10c6c316837c6c128f460f1aaba1ea
# first bad commit: [fb3bd914b3ec28f5fb697ac55c4846ac2d542855] x86/srso: Add a Speculative RAS Overflow mitigation
Not sure how helpful that will be...
Cheers,
Nathan
next prev parent reply other threads:[~2023-08-10 16:14 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
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 [this message]
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=20230810161414.GA4000@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®