From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "peterz@infradead.org" <peterz@infradead.org>,
"minipli@grsecurity.net" <minipli@grsecurity.net>
Cc: "x86@kernel.org" <x86@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Subject: Re: [PATCH] x86/shstk: Provide kernel command line knob to disable
Date: Thu, 2 Apr 2026 16:53:34 +0000 [thread overview]
Message-ID: <c4e8d271a2ff32f1e0a2315143862385c7ac346a.camel@intel.com> (raw)
In-Reply-To: <20260402160448.GD3738786@noisy.programming.kicks-ass.net>
On Thu, 2026-04-02 at 18:04 +0200, Peter Zijlstra wrote:
> > However, in at least one case the UEFI firmware was involved and I
> > had to test&debug on bare metal. Having such a knob allows ruling
> > out or pin-pointing CET as the cause more easily.
>
> Fair enough, although this should probably have made it in the
> Changelog.
>
> Other than that,
Some firmwares use supervisor shadow stack in SMM and have had issues
with CR4.CET set. But these were BIOS crashes.
The other usefulness could be recovering from shadow stack crashes in
early userspace that block boot.
Acked-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
Could we add something to the docs though?
next prev parent reply other threads:[~2026-04-02 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 15:44 Mathias Krause
2026-04-02 15:54 ` Peter Zijlstra
2026-04-02 15:59 ` Mathias Krause
2026-04-02 16:04 ` Peter Zijlstra
2026-04-02 16:53 ` Edgecombe, Rick P [this message]
2026-04-02 16:57 ` Dave Hansen
2026-04-02 17:38 ` Mathias Krause
2026-04-02 17:01 ` Mathias Krause
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=c4e8d271a2ff32f1e0a2315143862385c7ac346a.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=minipli@grsecurity.net \
--cc=peterz@infradead.org \
--cc=tglx@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
all inboxes | Powered by JetHome®