From: Borislav Petkov <bp@alien8.de>
To: Ronan Pigott <ronan@rjp.ie>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: UMIP and clearcpuid=
Date: Wed, 10 Jun 2026 13:00:54 -0700 [thread overview]
Message-ID: <20260610200054.GDainCdpF585khK77w@fat_crate.local> (raw)
In-Reply-To: <e60f6e46b74131ebaf54793be00618cf13727ede@rjp.ie>
On Wed, Jun 10, 2026 at 07:46:11PM +0000, Ronan Pigott wrote:
> In [1] the clearcpuid= flag was hidden, but afaik this remains the only way to
> disable UMIP.
The reason for wanting to disable it being?
> At the time UMIP was enabled, clearcpuid was apparently determined to be the
> appropriate method of disablement in [2],
Don't confuse "appropriate" with "might be good enough" ;)
> and it remains recommended by the documentation in [3].
That doc says:
"DO NOT USE this cmdline option in production - it is meant to be used only as
a quick’n’dirty debugging aid to rule out a feature-enabling code is the
culprit. If you use it, it’ll taint the kernel."
> If clearcpuid is no good, can we have a sanctioned method to disable UMIP
> protections instead then?
Let's figure out the use case first pls.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-06-10 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 19:46 UMIP and clearcpuid= Ronan Pigott
2026-06-10 20:00 ` Borislav Petkov [this message]
2026-06-10 20:41 ` Ronan Pigott
2026-06-10 23:55 ` Borislav Petkov
2026-06-11 7:53 ` Peter Zijlstra
2026-06-11 16:09 ` Borislav Petkov
2026-06-11 18:37 ` Peter Zijlstra
2026-06-12 2:21 ` Borislav Petkov
2026-06-12 6:42 ` Peter Zijlstra
2026-06-12 14:49 ` Borislav Petkov
2026-08-14 11:50 ` Peter Zijlstra
2026-08-14 12:12 ` Peter Zijlstra
2026-08-14 12:57 ` Andrew Cooper
2026-08-14 13:23 ` Peter Zijlstra
2026-08-17 21:39 ` Kenny Wottrich
2026-08-14 12:19 ` Peter Zijlstra
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=20260610200054.GDainCdpF585khK77w@fat_crate.local \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ronan@rjp.ie \
--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