From: Mathias Krause <minipli@grsecurity.net>
To: Borislav Petkov <bp@alien8.de>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH v3] x86/cpufeatures: Make X86_FEATURE_SHSTK clearcpuid-able
Date: Fri, 15 May 2026 18:20:46 +0200 [thread overview]
Message-ID: <bf9738e1-330e-4c87-a294-e8dce100ffc2@grsecurity.net> (raw)
In-Reply-To: <20260514223846.GJagZO9l17Aj0ZnI-K@fat_crate.local>
On 5/15/26 00:38, Borislav Petkov wrote:
> If you want to disable things, then you need to disable them properly. Like
> turn off CR4 bits in this case or disable dependent features in other cases.
> Or whatever else is needed.
>
> Whatever you do, it needs to have a use case and be properly done.
>
> clearcpuid= is simply shooting down X86_FEATURE flags. Not really well thought
> out but a wholesale quick'n'dirty method of toggling feature bits (yah,
> there's the setcpuid= counterpart too). And that's why it should not really
> exist but that ship has sailed...
>
So a "nocet" for that very use case of disabling CR4.CET, which would
simply disable X86_FEATURE_IBT and X86_FEATURE_SHSTK?
Thanks,
Mathias
next prev parent reply other threads:[~2026-05-15 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 16:09 [PATCH v3] x86/cpufeatures: Make X86_FEATURE_SHSTK clearcpuid-able Mathias Krause
2026-05-14 16:59 ` Borislav Petkov
2026-05-14 17:07 ` Edgecombe, Rick P
2026-05-14 17:12 ` Borislav Petkov
2026-05-14 17:15 ` Borislav Petkov
2026-05-14 18:23 ` Edgecombe, Rick P
2026-05-14 22:38 ` Borislav Petkov
2026-05-15 16:20 ` Mathias Krause [this message]
2026-05-14 17:30 ` Dave Hansen
2026-05-14 18:25 ` Edgecombe, Rick P
2026-05-15 16:11 ` Mathias Krause
2026-05-15 16:21 ` Edgecombe, Rick P
2026-05-14 17:01 ` 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=bf9738e1-330e-4c87-a294-e8dce100ffc2@grsecurity.net \
--to=minipli@grsecurity.net \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.