From: Samuele Cerea <samuele@cerea.dev>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, Samuele Cerea <samuele@cerea.dev>
Subject: [PATCH] x86 Handle trap flag when instruction is emulated
Date: Tue, 29 Jul 2025 23:44:33 +0200 [thread overview]
Message-ID: <20250729214433.734459-1-samuele@cerea.dev> (raw)
When the kernel emulates an instruction (for UIMP instruction emulation
and iopl emulation) the trap flag (TF) is currently ignored. As a result no
SIGTRAP event is delivered when the instruction is emulated successfully,
breaking the expected behavior for signle-stepping in debuggers.
This patch checks if the TF is set and sends the expected SIGTRAP signal
to the user. Other exception take precedence over the trap flag the SIGTRAP
signal is sent only if the emulation was successful.
The bug can be reproduced by signle-stepping in this code:
nop
sldt rax
sldt rax
nop
The two sldt instruction will be skipped an the debugger will step directly
to the second nop instruction.
Signed-off-by: Samuele Cerea <samuele@cerea.dev>
---
arch/x86/kernel/traps.c | 9 +++++++++
arch/x86/kernel/umip.c | 10 ++++++++++
2 files changed, 19 insertions(+)
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index 36354b470590..6e7d07a5f587 100644
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -705,6 +705,15 @@ static bool fixup_iopl_exception(struct pt_regs *regs)
}
regs->ip += 1;
+
+ /* If the instruction was emulated successfully, emulate trap flag */
+ if (regs->flags & X86_EFLAGS_TF) {
+ t->cr2 = regs->ip;
+ t->trap_nr = X86_TRAP_DB;
+ t->error_code = 0;
+ force_sig_fault(SIGTRAP, TRAP_TRACE, (void __user *)regs->ip);
+ }
+
return true;
}
diff --git a/arch/x86/kernel/umip.c b/arch/x86/kernel/umip.c
index 5a4b21389b1d..c4c462074f1d 100644
--- a/arch/x86/kernel/umip.c
+++ b/arch/x86/kernel/umip.c
@@ -342,6 +342,7 @@ bool fixup_umip_exception(struct pt_regs *regs)
unsigned long *reg_addr;
void __user *uaddr;
struct insn insn;
+ struct task_struct *tsk = current;
if (!regs)
return false;
@@ -407,5 +408,14 @@ bool fixup_umip_exception(struct pt_regs *regs)
/* increase IP to let the program keep going */
regs->ip += insn.length;
+
+ /* 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);
+ }
+
return true;
}
--
2.50.1
next reply other threads:[~2025-07-29 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:44 Samuele Cerea [this message]
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
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=20250729214433.734459-1-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®