From: Peter Zijlstra <peterz@infradead.org>
To: jpoimboe@kernel.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
alexandre.chartre@oracle.com
Subject: [PATCH 2/3] objtool/x86: Add UDB support
Date: Wed, 24 Sep 2025 15:45:09 +0200 [thread overview]
Message-ID: <20250924134644.027686159@infradead.org> (raw)
In-Reply-To: 20250924134507.288529132@infradead.org
Per commit 85a2d4a890dc ("x86,ibt: Use UDB instead of 0xEA"), make
sure objtool also recognises UDB as a #UD instruction.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
tools/objtool/arch/x86/decode.c | 4 ++++
1 file changed, 4 insertions(+)
--- a/tools/objtool/arch/x86/decode.c
+++ b/tools/objtool/arch/x86/decode.c
@@ -683,6 +683,10 @@ int arch_decode_instruction(struct objto
insn->type = INSN_SYSRET;
break;
+ case 0xd6: /* udb */
+ insn->type = INSN_BUG;
+ break;
+
case 0xe0: /* loopne */
case 0xe1: /* loope */
case 0xe2: /* loop */
next prev parent reply other threads:[~2025-09-24 13:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 13:45 [PATCH 0/3] objtool: Few x86 decoder updates Peter Zijlstra
2025-09-24 13:45 ` [PATCH 1/3] objtool/x86: Remove 0xea hack Peter Zijlstra
2025-09-25 9:55 ` Alexandre Chartre
2025-10-14 11:47 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2025-09-24 13:45 ` Peter Zijlstra [this message]
2025-09-25 9:56 ` [PATCH 2/3] objtool/x86: Add UDB support Alexandre Chartre
2025-10-14 11:47 ` [tip: objtool/core] " tip-bot2 for Peter Zijlstra
2025-09-24 13:45 ` [PATCH 3/3] objtool/x86: Fix NOP decode Peter Zijlstra
2025-09-24 17:34 ` Alexandre Chartre
2025-09-24 18:41 ` Peter Zijlstra
2025-09-25 9:55 ` Alexandre Chartre
2025-09-25 10:03 ` Peter Zijlstra
2025-09-25 10:42 ` Peter Zijlstra
2025-09-25 11:29 ` Andrew Cooper
2025-09-25 12:43 ` Peter Zijlstra
2025-09-25 13:04 ` Alexandre Chartre
2025-09-25 14:11 ` Peter Zijlstra
2025-09-25 13:05 ` Alexandre Chartre
2025-10-14 11:47 ` [tip: objtool/core] " tip-bot2 for 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=20250924134644.027686159@infradead.org \
--to=peterz@infradead.org \
--cc=alexandre.chartre@oracle.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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