From: Samuele Cerea <samuele@cerea.dev>
To: bp@alien8.de
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, dave.hansen@linux.intel.com,
Samuele Cerea <samuele@cerea.dev>
Subject: [PATCH v2] x86/traps: Handle trap flag when instruction is emulated
Date: Mon, 1 Sep 2025 18:25:28 +0200 [thread overview]
Message-ID: <20250901162527.18247-2-samuele@cerea.dev> (raw)
In-Reply-To: <20250822170107.GGaKiiU-HFkxnbymhY@fat_crate.local>
Simulate the trap flag (TF) behavior when the kernel emulates UIMP
instructions and iopl instructions.
When an instruction is emulated successfully and the TF is set, send a
SIGTRAP signal to the process, as it would happen for a normally
executed instruction.
Fix a problem with debuggers when signle-stepping instructions where
emulated instruction would get skipped.
Here is an example of the problem:
NOP
SLDT %rax
SLDT %rax
NOP
The two SLDT instructions will be skipped an the debugger will step
directly to the second NOP instruction.
Signed-off-by: Samuele Cerea <samuele@cerea.dev>
---
I fixed the issues you pointed out, hopefully now everything is correct
arch/x86/include/asm/traps.h | 2 ++
arch/x86/kernel/traps.c | 14 ++++++++++++++
arch/x86/kernel/umip.c | 1 +
3 files changed, 17 insertions(+)
diff --git a/arch/x86/include/asm/traps.h b/arch/x86/include/asm/traps.h
index 869b88061801..7742a6d05158 100644
--- a/arch/x86/include/asm/traps.h
+++ b/arch/x86/include/asm/traps.h
@@ -39,6 +39,8 @@ void math_emulate(struct math_emu_info *);
bool fault_in_kernel_space(unsigned long address);
+void emulate_trap_flag(struct pt_regs *regs);
+
#ifdef CONFIG_VMAP_STACK
void __noreturn handle_stack_overflow(struct pt_regs *regs,
unsigned long fault_address,
diff --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
@@ -678,6 +678,19 @@ static enum kernel_gp_hint get_kernel_gp_address(struct pt_regs *regs,
#define GPFSTR "general protection fault"
+void emulate_trap_flag(struct pt_regs *regs)
+{
+ struct task_struct *tsk = current;
+
+ /* If the instruction was emulated successfully, emulate trap flag */
+ if (regs->flags & X86_EFLAGS_TF) {
+ tsk->thread.cr2 = regs->ip;
+ tsk->thread.trap_nr = X86_TRAP_DB;
+ tsk->thread.error_code = 0;
+ force_sig_fault(SIGTRAP, TRAP_TRACE, (void __user *)regs->ip);
+ }
+}
+
static bool fixup_iopl_exception(struct pt_regs *regs)
{
struct thread_struct *t = ¤t->thread;
@@ -705,6 +718,7 @@ static bool fixup_iopl_exception(struct pt_regs *regs)
}
regs->ip += 1;
+ emulate_trap_flag(regs);
return true;
}
diff --git a/arch/x86/kernel/umip.c b/arch/x86/kernel/umip.c
index 5a4b21389b1d..8a5f33562bb4 100644
--- a/arch/x86/kernel/umip.c
+++ b/arch/x86/kernel/umip.c
@@ -407,5 +407,6 @@ bool fixup_umip_exception(struct pt_regs *regs)
/* increase IP to let the program keep going */
regs->ip += insn.length;
+ emulate_trap_flag(regs);
return true;
}
--
2.51.0
next prev parent reply other threads:[~2025-09-01 16:34 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 ` Samuele Cerea [this message]
2025-09-01 18:26 ` [PATCH v2] x86/traps: " Andrew Cooper
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=20250901162527.18247-2-samuele@cerea.dev \
--to=samuele@cerea.dev \
--cc=bp@alien8.de \
--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 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®