From: Andrew Cooper <andrew.cooper3@citrix.com>
To: samuele@cerea.dev
Cc: bp@alien8.de, dave.hansen@linux.intel.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH v2] x86/traps: Handle trap flag when instruction is emulated
Date: Mon, 1 Sep 2025 19:26:36 +0100 [thread overview]
Message-ID: <15270685-c5e0-40f6-91ff-87ff57fdd4d4@citrix.com> (raw)
In-Reply-To: <20250901162527.18247-2-samuele@cerea.dev>
> Simulate the trap flag (TF) behavior when the kernel emulates UIMP
> instructions and iopl instructions.
You'll want to do this for CPUID too when CPUID Faulting is active.
> diff
> <https://lore.kernel.org/lkml/20250901162527.18247-2-samuele@cerea.dev/#iZ31arch:x86:kernel:traps.c>
> --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c index
> 36354b470590..bea28473866b 100644 --- a/arch/x86/kernel/traps.c +++
> b/arch/x86/kernel/traps.c
> @@ -705,6 +718,7 @@ static bool fixup_iopl_exception(struct pt_regs
> *regs) }
>
> regs->ip += 1;
> + emulate_trap_flag(regs); return true;
> }
>
There's a fun bug in fixup_iopl_exception() which you're turning from
latent to real.
Not all STI/CLI instructions are 1 byte long. If they have a redundant
prefix, the old logic would simply brute-force through the instruction 1
prefix byte at a time.
But now, you'll generate SIGTRAP in the middle of the instruction.
~Andrew
prev parent reply other threads:[~2025-09-01 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:44 [PATCH] x86 " Samuele Cerea
2025-08-22 17:01 ` Borislav Petkov
2025-09-01 16:25 ` [PATCH v2] x86/traps: " Samuele Cerea
2025-09-01 18:26 ` Andrew Cooper [this message]
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=15270685-c5e0-40f6-91ff-87ff57fdd4d4@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=samuele@cerea.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®