From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] objtool fixes
Date: Thu, 10 Apr 2025 23:03:42 +0200 [thread overview]
Message-ID: <Z_gyLithD84kC30H@gmail.com> (raw)
Linus,
Please pull the latest objtool/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git objtool-urgent-2025-04-10
# HEAD: 87cb582d2f55d379ce95b5bcc4ec596e29b0a65e objtool: Fix false-positive "ignoring unreachables" warning
Merge note: I amended the top commit (87cb582d2f) shortly before the
pull request, to fix a changelog formatting error. Code was not
changed.
Miscellaneous objtool fixes:
- Remove the recently introduced ANNOTATE_IGNORE_ALTERNATIVE noise
from clac()/stac() code to make .s files more readable.
- Fix INSN_SYSCALL / INSN_SYSRET semantics
- Fix various false-positive warnings
Thanks,
Ingo
------------------>
Josh Poimboeuf (6):
objtool: Fix INSN_CONTEXT_SWITCH handling in validate_unret()
objtool: Split INSN_CONTEXT_SWITCH into INSN_SYSCALL and INSN_SYSRET
objtool: Stop UNRET validation on UD2
objtool, xen: Fix INSN_SYSCALL / INSN_SYSRET semantics
objtool: Remove ANNOTATE_IGNORE_ALTERNATIVE from CLAC/STAC
objtool: Fix false-positive "ignoring unreachables" warning
arch/x86/include/asm/smap.h | 12 ++++----
arch/x86/xen/xen-asm.S | 4 +--
tools/objtool/arch/x86/decode.c | 18 ++++++-----
tools/objtool/arch/x86/special.c | 2 +-
tools/objtool/check.c | 59 +++++++++++++++++++++++++++++++-----
tools/objtool/include/objtool/arch.h | 3 +-
6 files changed, 72 insertions(+), 26 deletions(-)
next reply other threads:[~2025-04-10 21:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 21:03 Ingo Molnar [this message]
2025-04-10 22:52 ` [GIT PULL] objtool fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-12-06 11:37 Ingo Molnar
2025-12-06 20:43 ` pr-tracker-bot
2025-04-01 19:57 Ingo Molnar
2025-04-02 17:48 ` pr-tracker-bot
2025-04-02 17:58 ` Linus Torvalds
2025-04-02 20:30 ` Ingo Molnar
2025-04-03 8:31 ` Josh Poimboeuf
2025-04-03 14:52 ` Ingo Molnar
2025-04-03 15:23 ` Josh Poimboeuf
2025-04-03 15:33 ` Ingo Molnar
2025-04-03 15:43 ` Josh Poimboeuf
2025-04-03 16:06 ` Linus Torvalds
2025-04-03 18:24 ` Josh Poimboeuf
2025-04-03 19:12 ` Linus Torvalds
2025-04-03 19:42 ` Josh Poimboeuf
2025-04-03 15:58 ` Linus Torvalds
2025-04-03 15:39 ` Linus Torvalds
2025-02-28 19:08 Ingo Molnar
2025-03-01 1:41 ` pr-tracker-bot
2021-06-24 6:54 Ingo Molnar
2021-06-24 16:34 ` pr-tracker-bot
2021-06-12 12:37 Ingo Molnar
2021-06-12 19:09 ` pr-tracker-bot
2021-05-15 7:46 Ingo Molnar
2021-05-15 17:55 ` pr-tracker-bot
2020-04-25 9:04 Ingo Molnar
2020-04-25 19:30 ` pr-tracker-bot
2018-11-30 6:18 Ingo Molnar
2018-11-30 21:00 ` pr-tracker-bot
2017-11-26 12:34 Ingo Molnar
2017-03-01 22:01 Ingo Molnar
2017-02-28 7:53 Ingo Molnar
2017-03-01 1:55 ` Linus Torvalds
2017-03-01 6:05 ` Josh Poimboeuf
2016-04-23 11:10 Ingo Molnar
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=Z_gyLithD84kC30H@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).