From: Dave Hansen <dave.hansen@intel.com>
To: Mathias Krause <minipli@grsecurity.net>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Rick Edgecombe <rick.p.edgecombe@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/shstk: Provide kernel command line knob to disable
Date: Wed, 6 May 2026 12:03:10 -0700 [thread overview]
Message-ID: <739e4dd0-84a3-4b37-8cc3-b7ec59737010@intel.com> (raw)
In-Reply-To: <3d7c8d26-558d-40ef-9ad9-3a5100eed9e5@grsecurity.net>
On 5/4/26 05:09, Mathias Krause wrote:
> +static int __init shstk_configure(char *str)
> +{
> + if (!strcmp(str, "off"))
> + setup_clear_cpu_cap(X86_FEATURE_SHSTK);
> +
> + return 1;
> +}
> +__setup("shstk=", shstk_configure);
Is there a reason that clearcpuid=shstk doesn't work in this case? I
guess shstk and ibt are peers, but I was kinda hoping we'd stop adding
these for every single CPU feature at _some_ point.
Adding the documentation for ibt= is definitely a good idea, though.
next prev parent reply other threads:[~2026-05-06 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 17:36 [PATCH v2] x86/shstk: Provide kernel command line knob to disable Mathias Krause
2026-05-04 12:09 ` Mathias Krause
2026-05-06 19:03 ` Dave Hansen [this message]
2026-05-06 22:45 ` 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=739e4dd0-84a3-4b37-8cc3-b7ec59737010@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox