From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Dan Snyder <dansnyder@google.com>
Subject: Re: [PATCH 0/3] x86/umip: Fix UMIP insn decoder false positives
Date: Fri, 19 Sep 2025 07:31:16 -0700 [thread overview]
Message-ID: <aM1pNN_ById_l6xR@google.com> (raw)
In-Reply-To: <20250808172358.1938974-1-seanjc@google.com>
On Fri, Aug 08, 2025, Sean Christopherson wrote:
> Fix two false positives scenarios where the UMIP #GP logic will incorrectly
> trigger emulation, e.g. due to a partially decoded instruction, or on
> instructions like VMLAUNCH that usurp the register form of '0f 01'.
>
> Tested with the hack-a-test patch at the end, but I haven't done any testing
> using a real userspace (neither positive nor negative testing).
>
> Sean Christopherson (3):
> x86/umip: Check that the instruction opcode is at least two bytes
> x86/umip: Fix decoding of register forms of 0F 01 (SGDT and SIDT
> aliases)
Ping on these two, looks like they slipped through the cracks. FWIW, I wouldn't
consider these urgent enough to squeeze into 6.17, but it'd be nice to get them
into 6.18.
next prev parent reply other threads:[~2025-09-19 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 17:23 [PATCH 0/3] x86/umip: Fix UMIP insn decoder false positives Sean Christopherson
2025-08-08 17:23 ` [PATCH 1/3] x86/umip: Check that the instruction opcode is at least two bytes Sean Christopherson
2025-08-14 14:42 ` Peter Zijlstra
2025-09-19 18:16 ` Borislav Petkov
2025-09-19 21:24 ` Sean Christopherson
2025-09-20 10:07 ` Borislav Petkov
2025-09-19 19:55 ` [tip: x86/cpu] " tip-bot2 for Sean Christopherson
2025-08-08 17:23 ` [PATCH 2/3] x86/umip: Fix decoding of register forms of 0F 01 (SGDT and SIDT aliases) Sean Christopherson
2025-08-14 14:42 ` Peter Zijlstra
2025-09-19 19:55 ` [tip: x86/cpu] " tip-bot2 for Sean Christopherson
2025-08-08 17:23 ` [PATCH 3/3] *** DO NOT MERGE *** x86/umip: Lazy person's KUnit test for UMIP emulation Sean Christopherson
2025-09-19 14:31 ` Sean Christopherson [this message]
2025-09-19 14:46 ` [PATCH 0/3] x86/umip: Fix UMIP insn decoder false positives Borislav Petkov
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=aM1pNN_ById_l6xR@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dansnyder@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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.