From: Mathias Krause <minipli@grsecurity.net>
To: Dave Hansen <dave.hansen@intel.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"x86@kernel.org" <x86@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@kernel.org" <tglx@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gao, Chao" <chao.gao@intel.com>
Subject: Re: [PATCH v2] x86/shstk: Provide kernel command line knob to disable
Date: Mon, 11 May 2026 07:04:44 +0200 [thread overview]
Message-ID: <13936b8a-4684-48a4-91eb-de0e1c2913ee@grsecurity.net> (raw)
In-Reply-To: <85cb14e7-403b-46fa-9e7d-819fef8d5a6d@intel.com>
On 08.05.26 18:34, Dave Hansen wrote:
> On 5/8/26 00:23, Mathias Krause wrote:
>> For *me*, 'clearcpuid=shstk,ibt' would be sufficient for my debugging
>> needs. It's just a question if there's more demand beside some random
>> kernel hacker needing a knob to disable potential problematic features,
>> i.e. do we expect actual *end users* having a need to fully disable CET
>> shadow stacks too?
>
> Last I checked, end users aren't frequently in the business of editing
> the kernel command line to turn off CPU features. Maybe once in a blue
> moon to work around bugs. But those folks can live with taint until they
> get fixes.
Ok, I'll drop this one and go for the 'clearcpuid=shstk' approach.
Thanks,
Mathias
next prev parent reply other threads:[~2026-05-11 5:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260402173606.1096172-1-minipli@grsecurity.net>
[not found] ` <3d7c8d26-558d-40ef-9ad9-3a5100eed9e5@grsecurity.net>
2026-05-06 19:03 ` [PATCH v2] x86/shstk: Provide kernel command line knob to disable Dave Hansen
2026-05-06 22:45 ` Edgecombe, Rick P
2026-05-07 13:39 ` Mathias Krause
2026-05-07 19:53 ` Edgecombe, Rick P
2026-05-08 7:23 ` Mathias Krause
2026-05-08 16:34 ` Dave Hansen
2026-05-11 5:04 ` Mathias Krause [this message]
2026-05-08 16:35 ` Edgecombe, Rick P
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=13936b8a-4684-48a4-91eb-de0e1c2913ee@grsecurity.net \
--to=minipli@grsecurity.net \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--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