From: Dave Hansen <dave.hansen@intel.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"minipli@grsecurity.net" <minipli@grsecurity.net>,
"bp@alien8.de" <bp@alien8.de>
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: Thu, 14 May 2026 10:30:29 -0700 [thread overview]
Message-ID: <a1a53fb5-1216-4ed2-b256-e2c8dc2d51bf@intel.com> (raw)
In-Reply-To: <8380b063f933ac3b909b6a5c9adfa03a116da1f7.camel@intel.com>
On 5/14/26 10:07, Edgecombe, Rick P wrote:
> Also, have you ever thought about keeping a list of approved clearcpuid values
> that are supported for normal runtime. People could use it to turn off features
> without picking up a taint?
What's wrong with taint?
"I got a bug report from Joe who has a system with feature $FOO and not
feature $BAR. I don't have that CPU, so I used clearcpuid=$BAR to help
reproduce the bug. Here's the oops I saw..."
We're not going to ignore that bug report. We're going to look at it a
bit closer and make sure the taint does appear to be from
clearcpuid=$BAR. But the taint is *FINE*.
next prev parent reply other threads:[~2026-05-14 17:30 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
2026-05-14 17:30 ` Dave Hansen [this message]
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=a1a53fb5-1216-4ed2-b256-e2c8dc2d51bf@intel.com \
--to=dave.hansen@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=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.